agentmods.dev

docs

docs is a skill for Claude Code from ericfitz/skills. It costs 71 tokens per session (1,169 once invoked), scanned A, original, Apache-2.0.

A skill for reading a project’s written records, such as requirements documents, specifications, design documents, and architecture decisions. It extracts what the system should do, how people use it, and which rules must remain true.

In plain words
What is it for?
Use it to profile a project, collect requirements, identify domain terms, and establish fixed system rules.
Why use it?
It helps an agent understand an unfamiliar project from its own documentation before making changes or gathering requirements.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the profile plugin — 4 skills shipped together

not rated 0repo changed 10d ago A scan 71 tokens original Apache-2.0

Good fit Use it to profile a project, collect requirements, identify domain terms, and establish fixed system rules.

Compare 6 skills from other repositories ↓
View source ↗ ericfitz/skills
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add ericfitz/skills
Claude Code
/plugin install profile

Made for: Claude Code.

Or install profile, the plugin that ships this one along with the rest of its 4 skills.

Wrote 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.

agentmods badge for docs

README.md
[![agentmods](https://agentmods.dev/badge/skills/ericfitz/skills/docs/github.svg)](https://agentmods.dev/skills/ericfitz/skills/docs)
Your own site
<a href="https://agentmods.dev/skills/ericfitz/skills/docs"><img src="https://agentmods.dev/badge/skills/ericfitz/skills/docs/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.

agentmods 80×15 button for docs

Your own site · 80×15
<a href="https://agentmods.dev/skills/ericfitz/skills/docs"><img src="https://agentmods.dev/badge/skills/ericfitz/skills/docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,169 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00071 $0.01169
Opus 5.5 $0.00028 $0.00468
Sonnet 5.5 $0.00014 $0.00234
Haiku 4.5 $0.00007 $0.00117

Measured 10d ago against content hash 5ceb0422e0e2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

docs 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 10d 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.

profile/skills/docs/SKILL.md · 100 lines

How it starts

The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.

docs

Read what this project wrote down about itself, and extract what it says the system is supposed to do.

This is the second gate phase: journeys, topology, and other consumers all read from the record this phase produces, so they read it once and agree about it.

Reference: ${CLAUDE_PLUGIN_ROOT}/references/doc-sources.md Contract: ${CLAUDE_PLUGIN_ROOT}/references/contracts/docs.schema.json Example: ${CLAUDE_PLUGIN_ROOT}/references/contracts/examples/docs.example.json

Usage

/profile:docs [path]

Input

You are normally handed a profile:stack contract; use inventory.docs and inventory.docs_sites as your in-repo census. You may also be handed external document pointers — URLs, wiki locations, local paths.

Standalone invocation: if you were not handed a stack contract, invoke profile:stack first and use its output. If you were not given external pointers and you are running in a conversation with the user, ask once whether any requirements documents, PRDs, or specifications live outside the repository, and accept "none".

Output location

Emit the contract as your reply; never write it into the target repo.

Procedure

  1. Resolve sources. For each in-repo document, the capability is Read. For each external pointer, match it to a capability that is already available in this session per the source-tier table. Record every resolved source in sources_available[] with the capability you used.

  2. Record what you cannot reach. A pointer with no matching capability goes in unavailable_sources[] with a reason and a suggested_remedy drawn from the remedy table. Then continue — an unreachable source is a reported gap, never a stop.

  3. Census. For every candidate, record locator, title, headings, and last_modified. Correct the inventory's doc_type_guess, which is a path-based guess made without reading anything.

  4. Rank by the signals in the reference, in the order given.

  5. Deep-read down the ranking to the 25-document budget. Each document read becomes a corpus[] entry with read: full or read: skimmed and an authority value. Everything below the line becomes a deferred[] entry.

Read the full file on GitHub · 100 lines

Changes

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.

  1. 10d ago Changed · +4 lines 5ceb0422e0e2
  2. 1mo ago First seen · 96 lines · 71 tokens per session scan A aaba6d895f7e

Subscribe to this mod's changes

docs is a skill published in the GitHub repository ericfitz/skills (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 71 tokens to every session and 1,169 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-08-31.

Writing and docs
Related

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens