Coding Agent Security

Operating procedure for securing and evaluating AI coding agents and their generated (vibe-coded) code, distilled from Google's Kaggle whitepaper "Vibe Coding Agent Security and Evaluation" (May 2026): the Effective Trust model, the 7-Pillar Agent Security Architecture, threat classes specific to agent-written code (slopsquatting, MCP spoofing, invisible payloads, intent drift), and the 7-dimension evaluation framework with pre-ship gates. Use when running, sandboxing, reviewing, or shipping agent-generated code, hardening an agent harness or CI pipeline, gating high-stakes agent actions, or b

10 stars 2 forksAI, LLMs & Agents

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Archive228/lab-skills --skill coding-agent-security
Manual install
git clone --depth 1 https://github.com/Archive228/lab-skills.git /tmp/lab-skills
mkdir -p ~/.claude/skills
cp -r /tmp/lab-skills/skills/coding-agent-security ~/.claude/skills/coding-agent-security

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Coding Agent Security & Evaluation (Effective Trust)

This skill turns Google's "Vibe Coding Agent Security and Evaluation" whitepaper (Kartakis, Eidelman, Bakkali, Subasioglu — May 2026) into a work-time procedure: how to contain a coding agent (the 7-Pillar Agent Security Architecture under a continuous Effective Trust model), which threat classes are specific to agent-generated code, and which evaluation gates must pass before agent-written code ships. Core framing: security tells you whether the agent stayed inside the boundary; evaluation tells you whether what happened inside that boundary is worth shipping. An agent can pass every security check and still misread intent, ignore project conventions, or silently degrade UX — you must run both halves.

## When to use

- You are about to execute, review, merge, or deploy code generated by an AI coding agent (including your own output).
- You are designing or hardening the harness, sandbox, identity, or CI/CD pipeline around a coding agent.
- You are adding a tool/MCP server, a new dependency, or pasted third-party context (repos, forum posts, RAG data) to an agent workflow.
- You are building or running an eval suite to decide whether a coding agent's output is deployable.
Read the full skill on GitHub

Details

Skill name
coding-agent-security
Path
skills/coding-agent-security/SKILL.md
License
MIT
Repo updated
12 August 2026

FAQ

What does the Coding Agent Security skill do?

Operating procedure for securing and evaluating AI coding agents and their generated (vibe-coded) code, distilled from Google's Kaggle whitepaper "Vibe Coding Agent Security and Evaluation" (May 2026): the Effective Trust model, the 7-Pillar Agent Security Architecture, threat classes specific to agent-written code (slopsquatting, MCP spoofing, invisible payloads, intent drift), and the 7-dimension evaluation framework with pre-ship gates. Use when running, sandboxing, reviewing, or shipping agent-generated code, hardening an agent harness or CI pipeline, gating high-stakes agent actions, or b

How do I install the Coding Agent Security skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add Archive228/lab-skills --skill coding-agent-security. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Coding Agent Security popular?

It lives in Archive228/lab-skills, which has 10 GitHub stars and 2 forks.

Related skills

Agent Design Fundamentals

10

Archive228/lab-skills

Decision rules for whether to build an LLM agent and how to architect it, distilled from OpenAI's "A Practical Guide to Building Agents": build/no-build criteria, model selection, tool design, single-agent vs multi-agent orchestration (manager pattern vs decentralized handoffs), layered guardrails, and human-in-the-loop triggers. Use when designing, reviewing, or refactoring an agent system — before choosing an architecture, adding more agents, defining tools, or shipping an agent to production without guardrails.

AI, LLMs & Agents

Agent Evals

10

Archive228/lab-skills

Build and maintain evaluation suites for AI agents: bootstrap 20-50 tasks from real failures, pick code-based vs model-based vs human graders by agent architecture (coding, conversational, research, computer-use), write unambiguous tasks with reference solutions, and keep suites alive via ownership and transcript reading. Use when creating evals from zero, adding graders or eval cases, debugging suspicious eval scores, or deciding pass@k vs pass^k metrics for an agent product.

AI, LLMs & Agents

Agent Failure Preflight

10

Archive228/lab-skills

Pre-deployment failure-mode gate for agentic AI systems, distilled from Microsoft AI Red Team's Taxonomy of Failure Modes in Agentic AI Systems v2.0 (grounded in 12 months of red-team engagements). Run it before shipping or materially changing an agent — adding tools/MCP servers/plugins, enabling persistent memory, adding sub-agents or orchestration, enabling computer use, or expanding permissions — to verify concrete controls against memory poisoning, HitL bypass, goal hijacking, supply-chain compromise, session context contamination, capability disclosure, and multi-agent cascade failures.

AI, LLMs & Agents

Context Compression

10

Archive228/lab-skills

Compress an agent's context — long environment observations and accumulated interaction history — on long-horizon tasks using Microsoft's ACON method: threshold-triggered LLM compression with guidelines optimized from contrastive failure analysis. Trigger when an agent loop's context grows across many tool-call steps and blows token budgets or degrades decisions, when designing what a summarizer/compressor must preserve, or when distilling a compressor into a smaller model.

AI, LLMs & Agents

Cinema4d MCP

9

vladmdgolam/agent-skills

Cinema 4D MCP expert for extracting scene data, writing C4D Python scripts, and controlling Cinema 4D through MCP tools. Activate when: (1) using cinema4d MCP tools (get_scene_info, list_objects, execute_python_script, add_primitive, etc.), (2) writing Python scripts for Cinema 4D extraction or manipulation, (3) working with MoGraph cloners/effectors/fields, (4) baking animation data from C4D scenes, (5) debugging C4D Python API errors, (6) extracting Redshift material or camera data. Covers critical gotchas, correct extraction patterns, MoGraph baking, timeline evaluation, API compatibility,

AI, LLMs & Agents

Context Engineering

10

Archive228/lab-skills

Engineer an agent's context window as a finite attention budget: prompt at the right altitude, give judgment instead of rigid rules, use expressive tools and progressive disclosure over piled-up instructions, delete redundancy, and manage long-horizon runs with compaction, notes, and sub-agents. Trigger whenever you write or audit a system prompt, CLAUDE.md, skill, or tool set for an agent; when an agent ignores instructions or degrades on long runs; or when migrating prompts to Claude 5-generation models.

AI, LLMs & Agents

Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.