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 skills add ai-driven-dev/framework --skill 00-initgit clone --depth 1 https://github.com/ai-driven-dev/frameworkWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/ai-driven-dev/framework/00-init)<a href="https://agentmods.dev/skills/ai-driven-dev/framework/00-init"><img src="https://agentmods.dev/badge/skills/ai-driven-dev/framework/00-init/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ai-driven-dev/framework/00-init"><img src="https://agentmods.dev/badge/skills/ai-driven-dev/framework/00-init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00067 | $0.00567 |
| Opus 5.5 | $0.00027 | $0.00227 |
| Sonnet 5.5 | $0.00013 | $0.00113 |
| Haiku 4.5 | $0.00007 | $0.00057 |
Grade A, and why
00-init 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 11d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Init
flowchart TD
request([request]) --> probe{"aidd answers telemetry?"}
probe -->|"no"| absent([say it is missing, change nothing])
probe -->|"yes"| route{which case}
route -->|"start measuring"| start --> done([reported as it ran])
route -->|"name me, or stop naming me"| identity --> done
route -->|"stop measuring"| stop --> done
route -->|"delete what was measured"| forget
forget -->|"person confirms the preview"| done
forget -->|"person declines"| kept([nothing removed])
Actions
Run the flow above. Read only the action file the case needs.
| Action | Does |
|---|---|
| start | ask for consent, then turn measurement on for this project |
| identity | set, show or remove the name on the person's own measurement |
| stop | turn measurement off for this project, keeping what was measured |
| forget | preview, then on confirmation delete everything measured on this machine |
Transversal rules
- Probe first. Run
aidd telemetry on --helpbefore any action. Whenaiddis not found, the command exits non-zero, or its help does not list--anonymous, stop and say plainly thataiddis missing or too old to measure, name@ai-driven-dev/clias what to install or update, and state that nothing was changed. Never go on, and never answer as if it had worked. - Every change goes through
aidd telemetry. Never edit git config,.aidd/config.jsonor any file by hand. - Never run a command that changes anything before the person has said yes to what it does. A silence, a previous yes to another case, or a standing instruction is not a yes.
- Report what each command printed, including every warning, and never claim a result the output did not show.
- Never choose, derive or guess a name for the person: not from git, from the machine, nor from the session. Only the identifier the person types is used.
aidd telemetry onrun in a terminal offers the git name itself. - When a command exits non-zero, show its message and stop. Do not retry with other flags.
What ships with it
4 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.
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.
- 11d ago Changed · -17 lines · -32 tokens per session db7924768c35
- 1mo ago First seen · 58 lines · 99 tokens per session scan A 528cf1d00eea
00-init is a skill published in the GitHub repository ai-driven-dev/framework (538 stars, last pushed today), licensed MIT. It adds 67 tokens to every session and 567 once invoked, about $0.0003 per session on Opus 5.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-09-09.
Other skills, from other repositories
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.
skill-reviewer
Reviews DeerFlow skill packages for readiness, triggers, safety boundaries, resources, and evidence. Invoke when users ask to audit, grade, or production-check an existing skill.
knowledge-org
A guide to organising large bodies of knowledge so an AI system can navigate relationships, summaries, and layers instead of searching only flat text chunks. It covers tree indexes, knowledge graphs, file-like structures, incremental updates, and long-term memory layouts.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
git-checkpoint
Use git as a safety net - create a checkpoint commit before risky or large changes and roll back cleanly if a change makes things worse. Use before multi-file refactors.
kb-builder
Build an Obsidian-compatible knowledge base from public web sources using the TinyFish CLI. Use this skill when a user wants a builder-grade markdown knowledge base on a technical topic, asks for a structured research vault, or wants a topic compiled from live public sources into interlinked markdown files. Supports…