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 djscheuf/agentic-dev-ecosystem-template --skill create-knowledge-skillgit clone --depth 1 https://github.com/djscheuf/agentic-dev-ecosystem-templateWrote 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/djscheuf/agentic-dev-ecosystem-template/create-knowledge-skill)<a href="https://agentmods.dev/skills/djscheuf/agentic-dev-ecosystem-template/create-knowledge-skill"><img src="https://agentmods.dev/badge/skills/djscheuf/agentic-dev-ecosystem-template/create-knowledge-skill/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/djscheuf/agentic-dev-ecosystem-template/create-knowledge-skill"><img src="https://agentmods.dev/badge/skills/djscheuf/agentic-dev-ecosystem-template/create-knowledge-skill.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.00032 | $0.01723 |
| Opus 5.5 | $0.00013 | $0.00689 |
| Sonnet 5.5 | $0.00006 | $0.00345 |
| Haiku 4.5 | $0.00003 | $0.00172 |
Grade A, and why
create-knowledge-skill 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 20d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Act as an expert in Context Engineering, Progressive Disclosure, and AI Skill creation. Your job is to turn an external documentation source into a well-organized, context-efficient Agent skill (SKILL.md + supporting reference files) that future agents can consult instead of re-reading the source docs.
You will receive a base documentation url. You may also receive some guidance about what area to emphasize.
You must discuss with user at key checkpoints, maintaining an easy, conversational tone.
1. gather-inputs
- Check whether the invocation already supplied:
- Base documentation URL (REQUIRED) — the root/index page of the docs to capture
- Capture guidance (OPTIONAL) — a high-level description of what the skill should focus on capturing (e.g. "configuration options and custom providers," "just the CLI reference," "everything a developer needs to build integrations")
- If the base documentation URL is missing: STOP and ask the user for it directly. Do not guess or invent a URL.
- If capture guidance is missing: Ask the user once — e.g. "Anything specific you want this skill to focus on capturing, or should I determine the scope myself from the docs' structure?"
- If the user skips or declines, proceed autonomously: infer scope from the documentation's own structure (nav/table of contents) and prioritize broad, practical, actionable coverage over completeness.
- Once the URL is provided (and guidance is either given or explicitly skipped), proceed to step 2 without further questions.
2. survey-documentation
// turbo
- Fetch the base documentation URL and its navigation/table of contents
- Map the full documentation structure: sections, subsections, and major concepts (e.g. "Configuration," "CLI Reference," "Providers," "Extending")
- Note where deep-dive content lives (individual pages) vs. overview/index content
- Identify the pieces most relevant to the capture guidance from step 1 — or, if none was given, the pieces most likely to matter for someone building with/on top of this tool without repeatedly consulting the live docs
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.
- 20d ago Changed · +4 lines 16b87d73a033
- 22d ago First seen · 123 lines · 32 tokens per session scan A a0101b0ac558
create-knowledge-skill is a skill published in the GitHub repository djscheuf/agentic-dev-ecosystem-template (12 stars, last pushed 20d ago), licensed MIT. It adds 32 tokens to every session and 1,723 once invoked, about $0.0001 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-10-01.
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…