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 instructions/codealive-ai/ai-driven-development/agents-mdgit clone --depth 1 https://github.com/CodeAlive-AI/ai-driven-developmentWhat 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.01110 | $0.01110 |
| Opus 5 | $0.00555 | $0.00555 |
| Sonnet 5 | $0.00222 | $0.00222 |
| Haiku 4.5 | $0.00111 | $0.00111 |
Grade A, and why
ai-driven-development AGENTS.md 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 yesterday.
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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI-Driven Development — Development Guide
This repo is a single-plugin marketplace and a cross-agent skill collection in one. The same skills/ directory at the repo root is read by both npx skills add (the cross-agent CLI) and Claude Code's plugin install (/plugin marketplace add + /plugin install …@ai-driven-development). The plugin sees the repo root as itself via source: "./" in marketplace.json — no nesting, no symlinks, no duplication.
Git publishing defaults
When the user asks to commit or push without naming a target branch, commit and
push directly to main. If the current branch is main, stay on it; do not
create a feature branch by default. Use another branch only when the user
explicitly requests one.
When to create tags and releases
Only create git tags and GitHub releases when skill, hook, or plugin files change.
Requires a new tag/release
skills/*/— any skill file changes (SKILL.md, scripts, references, assets)hooks/*/— any hook source changes (Go code, install scripts, hook configs).claude-plugin/plugin.json— plugin manifest changes.claude-plugin/marketplace.json— marketplace catalogue changesLICENSE— licence changes
Examples:
- Adding a new skill or hook
- Updating skill instructions in SKILL.md
- Modifying skill scripts
- Changing plugin metadata or version
Does NOT require a new tag/release
Documentation-only changes don't need tagging:
README.md— documentation and use-case updatesAGENTS.mdand theCLAUDE.mdimport shim — repository instructions- Commit messages
- GitHub-specific files (
.github/*)
Rationale: users install specific commits via SHA. Documentation updates don't affect functionality, so they don't need version bumps. This keeps the release history clean.
README maintenance
The repo ships English-only. When you add or remove a skill, or change a skill description:
- Update the relevant section table in
README.md - Update the skill's own
SKILL.md(agent-facing) andREADME.md(human-facing, optional) - Update
.claude-plugin/plugin.jsonand.claude-plugin/marketplace.jsonversions
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.
- yesterday First seen · 101 lines · 1,110 tokens per session scan A 64a2dcc4263f
ai-driven-development AGENTS.md is an instructions file published in the GitHub repository CodeAlive-AI/ai-driven-development (131 stars, last pushed 3d ago), licensed MIT. It adds 1,110 tokens to every session, about $0.0056 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 instructions, from other repositories
parallel-code CLAUDE.md
Instructions for johannesjo/parallel-code, covering parallel code, stack, commands, project structure and conventions.
agents AGENTS.md
Instructions for scarletkc/agents, covering agent guidelines, environment, engineering principles, code style and testing.
codex-manager AGENTS.md
Instructions for ewsun22/codex-manager, covering codex manager 项目指令, 产品边界, 隐私与安全, 工程规则 and 开源文档与发布流程.
cladding CLAUDE.md
Instructions for qwerfunch/cladding, covering maintainer guide for ai-assisted work on cladding, spec authoring — always hash, never f-nnn, version bumps — use the script, detector additions — count is auto-recomputed and plugin manifest mirrors — built, not hand-authored.
cladding AGENTS.md
Instructions for qwerfunch/cladding, covering agents.md, 1. project, 2. setup, 3. verify before pushing and 4. code & comment style.
SubFrame AGENTS.md
Instructions for Codename-11/SubFrame, covering subframe - subframe project, core working principle, relationship to native ai tools, session start and concurrent work & worktrees.