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 toolsgit 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/tools)<a href="https://agentmods.dev/skills/ai-driven-dev/framework/tools"><img src="https://agentmods.dev/badge/skills/ai-driven-dev/framework/tools/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/tools"><img src="https://agentmods.dev/badge/skills/ai-driven-dev/framework/tools.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.00137 | $0.01075 |
| Opus 5.5 | $0.00055 | $0.00430 |
| Sonnet 5.5 | $0.00027 | $0.00215 |
| Haiku 4.5 | $0.00014 | $0.00108 |
Grade A, and why
tools 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 1mo 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.
Tools
tools is what the project targets and how each target is configured. Every AI assistant and
IDE the CLI supports is one AiTool<C> or IdeToolConfig object in
contexts/tools/domain/profiles/<tool>/profile.ts, where C is the intersection of Has*
capability interfaces the tool actually supports. translate depends on tools (never the
reverse) to call the tool's own rewriteContent and to read its build contract — a tool profile
is data and behavior the rest of the CLI is handed, not a place that reaches out to fetch or
install anything itself.
What goes in
| Concept | Location |
|---|---|
| A tool's identity, capabilities, content-rewrite | domain/profiles/<tool>/profile.ts |
A tool's aidd translate build behavior |
domain/profiles/<tool>/build.ts (only if the tool is a build target) |
| A string transform used by exactly one profile | that profile's own directory |
| A string transform shared by ≥2 profiles | domain/formats/ |
| A content-translation capability class (agents/skills/commands/rules/hooks) | domain/capabilities/ + a Has* entry in contracts.ts |
| Catalog/manifest shaping shared by ≥2 tools' build contracts | domain/marketplace-catalog.ts |
A port only tools needs |
domain/ports/ |
| A tool's own plugin-CLI driver | infrastructure/ |
How
AiTool<C>fields: readdomain/contracts.ts. A list copied here aged at every field.Has*interfaces live incontracts.ts, alwaysreadonly, never optional — a tool either includesHas<Name>in itsCintersection or does not have the field at all. Guard presence with"name" in tool.capabilities, neverinstanceof.rewriteContent(content)is one way, per tool, with no reverse and no shared base helper. Seereferences/content-rewrite.md.- A capability class ends in
Capability, takes one params object, all fieldsreadonly, throwsCapabilityConfigError(fromkernel/errors.ts) on an invalid combination, carries no application/infrastructure imports. Seereferences/capability-conventions.md. PluginsCapabilityhas three modes (native,flat,unsupported) and atranslationMode(marketplace|flat|null) — seereferences/plugins-capability.md.- Build behavior is ONE artifact-symmetric
ToolBuildContractper tool, read by the two mode-generic orchestrators (MarketplaceBuildStrategy,FlatBuildStrategy) intranslate— never a per-tool strategy class, never a per-tool or per-artifact-kind branch in an orchestrator. Seereferences/build-contract.md. registerTool(config)is called once, at the bottom ofprofile.ts, never from a use-case.- Follow the port/adapter rule in
.claude/rules/00-architecture/for the shape of a port and its adapter, and the shared-module rule there before promoting a helper out of a single profile.
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.
- 1mo ago First seen · 73 lines · 137 tokens per session scan A 5791d484e3b9
tools is a skill published in the GitHub repository ai-driven-dev/framework (518 stars, last pushed today), licensed MIT. It adds 137 tokens to every session and 1,075 once invoked, about $0.0005 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
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.
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.