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 eficode/modern-ai-developer-stack --skill example-update-readme-taxonomygit clone --depth 1 https://github.com/eficode/modern-ai-developer-stackWrote 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/eficode/modern-ai-developer-stack/example-update-readme-taxonomy)<a href="https://agentmods.dev/skills/eficode/modern-ai-developer-stack/example-update-readme-taxonomy"><img src="https://agentmods.dev/badge/skills/eficode/modern-ai-developer-stack/example-update-readme-taxonomy/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/eficode/modern-ai-developer-stack/example-update-readme-taxonomy"><img src="https://agentmods.dev/badge/skills/eficode/modern-ai-developer-stack/example-update-readme-taxonomy.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.00000 | $0.01033 |
| Opus 5.5 | $0.00000 | $0.00413 |
| Sonnet 5.5 | $0.00000 | $0.00207 |
| Haiku 4.5 | $0.00000 | $0.00103 |
Grade A, and why
example-update-readme-taxonomy 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 2mo 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Example Skill: Update README Taxonomy
Skill Purpose
Help an AI agent safely update the taxonomy and tool listings in README.md while preserving structure, style, and consistency with this repository's goals.
When to Use This Skill
- You want to add, move, or remove tools from the main stack.
- You need to introduce a new category or rename an existing one.
- You are cleaning up descriptions to stay aligned with developer-focused, non-marketing language.
Inputs
change_intent: short description of what should change (e.g. "add NotebookLM to Enterprise Knowledge").proposed_entries(optional): list of proposed Markdown bullets for new or updated tools.target_section(optional): name of the target section or subsection inREADME.md.constraints(optional): extra rules, e.g. "do not rename existing categories".
High-Level Workflow
- Inspect the current taxonomy and relevant sections in
README.md. - Build a clear, minimal change plan that matches
change_intent. - Apply edits in a way that preserves structure, style, and ordering.
- Re-scan the file to confirm consistency and formatting.
Detailed Agent Instructions
When this skill is invoked, follow these steps:
-
Load README
- Read
README.mdfrom the repo root. - Identify top-level sections (e.g. "Core Development", "Architecture", "Building & Orchestrating Agents").
- Read
-
Understand the Intent
- Parse
change_intentinto one or more concrete actions, such as:- Add a new tool entry.
- Update the description of an existing tool.
- Move a tool between categories.
- Rename or add a category.
- If
proposed_entriesis provided, treat them as suggestions; adjust wording to fit house style.
- Parse
-
Locate Target Section
- If
target_sectionis provided, match it to a heading inREADME.md(case-insensitive). - If not provided, infer the best section based on the tool's purpose using the existing taxonomy.
- If no reasonable match exists, consider whether a new subsection is warranted and include that in your plan.
- If
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.
- 2mo ago First seen · 117 lines · 0 tokens per session scan A 40d35dd8ad32
example-update-readme-taxonomy is a skill published in the GitHub repository eficode/modern-ai-developer-stack (14 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,033 tokens. 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…