Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sflandergan/agentic-codingnpx agentmods add skills/sflandergan/agentic-coding/feature-documentationWrote 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/sflandergan/agentic-coding/feature-documentation)<a href="https://agentmods.dev/skills/sflandergan/agentic-coding/feature-documentation"><img src="https://agentmods.dev/badge/skills/sflandergan/agentic-coding/feature-documentation/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/sflandergan/agentic-coding/feature-documentation"><img src="https://agentmods.dev/badge/skills/sflandergan/agentic-coding/feature-documentation.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.00022 | $0.00711 |
| Opus 5.5 | $0.00009 | $0.00284 |
| Sonnet 5.5 | $0.00004 | $0.00142 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
feature-documentation 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compact Feature Maps
Purpose and applicability
A feature map gives a compact overview of what has been built for a named capability, then points to the main packages and stable entry points used to extend it, and finally notes the non-obvious decisions that constrain extending it. It is not durable documentation for every endpoint, UI, job, fix, or delivery.
- A feature map exists only when it materially helps an engineer understand or extend a named capability or exposes a non-obvious ADR constraint.
- Omit or merge a map when the capability does not stand alone or its packages are already clear from a broader map.
- API and frontend surfaces of one capability belong in one map unless each surface is independently extendable.
- Prefer one map per durable package-spanning capability; do not create refinement or workflow-stage micro-maps.
Required investigation
- Start from the completed diff and changed packages; group affected files by package or feature-module root.
- Read
docs/features/README.mdand neighboring maps to detect overlap. - Verify the current package roots and stable entry points in source.
- Load applicable architecture guides independently for correctness; do not add them as map back-references.
- Read only ADRs whose non-obvious decisions may constrain the capability.
- Decide to create, update, merge, rename, remove, or omit the map before writing.
Default shape
# <Capability> Feature Map
<Two or three present-tense sentences: what the built capability does, who owns it,
and the boundary with adjacent capabilities.>
## Main Packages and Entry Points
- `<package-or-feature-module-root>/` — why an engineer starts here.
- `<stable-entry-file>` — include only when opening the package root is insufficient.
## Non-obvious Decisions
- [ADR NNNN](../adr/NNNN-slug.md) — the constraint this decision imposes.
## Non-obvious Decisions is optional and omitted when no qualifying ADR exists. No ## Architecture References or mandatory ## Scope section is allowed.
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 Changed · -44 lines · +6 tokens per session 969cd196335b
- 1mo ago First seen · 105 lines · 16 tokens per session scan A df08dd421c60
feature-documentation is a skill published in the GitHub repository sflandergan/agentic-coding (4 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 711 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-08-31.
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…