Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/ai-driven-dev/framework/03-context-generatenpx skills add ai-driven-dev/framework --skill 03-context-generategit clone --depth 1 https://github.com/ai-driven-dev/frameworkWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00112 | $0.01097 |
| Opus 5 | $0.00056 | $0.00549 |
| Sonnet 5 | $0.00022 | $0.00219 |
| Haiku 4.5 | $0.00011 | $0.00110 |
Grade A, and why
aidd-context:03:context-generate scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Generate
Generates the three context artifacts a project consumes:
- Skills - router-based:
SKILL.mdrouter + atomic testable actions, evaluations declared before implementation. - Agents - single-file agent definitions following the framework's agent template.
- Rules - framework rule files that govern editor/agent behavior.
Skill-generation actions
| # | Action | Role | Input |
|---|---|---|---|
| 01 | capture-intent |
Clarify output + decide generate vs modify | user intent |
| 02 | design-evals |
Write minimal scenarios.json |
expected output |
| 03 | decompose-actions |
List actions + their tests | evals + output |
| 04 | draft-skill |
Write SKILL.md router | decomposed actions |
| 05 | write-actions |
Write each action file | validated SKILL.md |
| 06 | validate |
Spawn one agent per action, run its ## Test, aggregate into a pass/fail report |
complete skill |
Files: actions/skills/01-capture-intent.md … actions/skills/06-validate.md.
Other generation actions
actions/agents/01-generate-agent.md- generate a project agent file fromassets/agents/agent-template.md.actions/rules/01-generate-rules.md- generate framework rules fromassets/rules/rule-template.md.
Default skill flow
01 → 02 → 03 → 04 → 05 → 06. After each action, run its ## Test before moving to the next. Action 02 self-skips when 01 outputs invocation_mode = manual.
Modify flow
01 (detects modify) → 03 (re-decompose if structure changes) → 05 (targeted edit) → 06 (re-validate).
Runtime tracking
Materialize the flow as a task list at skill entry; a task closes only when its ## Test passes.
Rules
- R1 - SKILL.md is a pure router: description + action table + transversal rules. Zero business logic.
- R2 - One skill = one domain (tool OR activity). Tool → singular noun (
slack); activity → action verb (review). Seereferences/naming-conventions.md. - R3 - References one-level deep. Never chain reference → reference.
- R4 - SKILL.md ≤ 500 lines. If exceeded, split into references.
- R5 - Description must include: what, explicit triggers, "Do NOT use for..." clause.
- R6 - Zero duplication. Templates live in
assets/; actions point to them via@<path>. - R7 -
references/= documents to READ (conventions, cheatsheets).assets/= files to COPY or INJECT (templates, ID tables). - R8 - Every action has a
## Test: one sentence describing how to verify its intent - a command to run, a concrete check on the produced artifact, or an observable side-effect (API/MCP/state). - R9 - Auto-trigger skills (
disable-model-invocation: false, default) shipevals/scenarios.json= JSON array of at least 3{prompt, expect_action}. Manual-only skills skip. - R10 - Generated skills are written in English only (frontmatter, body, actions, references, assets). Holds regardless of conversation language.
What ships with it
20 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- actions/agents/01-generate-agent.md 1.7 KB
- actions/rules/01-generate-rules.md 2.9 KB
- actions/skills/01-capture-intent.md 1.8 KB
- actions/skills/02-design-evals.md 953 B
- actions/skills/03-decompose-actions.md 2.6 KB
- actions/skills/04-draft-skill.md 1.0 KB
- actions/skills/05-write-actions.md 2.3 KB
- actions/skills/06-validate.md 2.7 KB
- assets/agents/agent-template.md 784 B
- assets/rules/rule-template.md 327 B
- assets/skills/action-template.md 1.0 KB
- assets/skills/evals-template.md 850 B
- assets/skills/skill-template.md 1.6 KB
- evals/scenarios.json 612 B
- references/agents-coordination.md 3.6 KB
- references/ai-mapping.md 5.7 KB
- references/naming-conventions.md 2.9 KB
- references/rule-structure.md 1.8 KB
- references/rule-writing.md 474 B
- references/skill-structure.md 1.7 KB
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 73 lines · 0 tokens per session scan A 94b9151a75e8
aidd-context:03:context-generate is a skill published in the GitHub repository ai-driven-dev/framework (445 stars, last pushed 2d ago), licensed MIT. It adds 112 tokens to every session and 1,097 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
smoke-test
End-to-end smoke test skill for DeerFlow. Guides through: 1) Pulling latest code, 2) Docker OR Local installation and deployment (user preference, default to Local if Docker network issues), 3) Service availability verification, 4) Health check, 5) Final test report. Use when the user says "run smoke test", "smoke…
image-generation
Use this skill when the user requests to generate, create, imagine, or visualize images including characters, scenes, products, or any visual content. Supports structured prompts and reference images for guided generation.
podcast-generation
Use this skill when the user requests to generate, create, or produce podcasts from text content. Converts written content into a two-host conversational podcast audio format with natural dialogue.
vercel-deploy
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.
zeroclaw
Help users operate and interact with their ZeroClaw agent instance — through both the CLI (zeroclaw commands) and the REST/WebSocket gateway API. Use this skill whenever the user wants to: send messages to ZeroClaw, manage memory or cron jobs, check system status, configure channels or providers, hit the gateway API…
github-issue-triage
Issue triage and lifecycle management agent for ZeroClaw. Use this skill whenever the user wants to: triage open issues, close stale/duplicate/fixed issues, apply labels, run a backlog sweep, enforce the current issue stale policy, or handle a specific issue. Trigger on: 'triage issues', 'issue triage', 'sweep…