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 agentmods add agents/sniko/agent-skills/documentationgit clone --depth 1 https://github.com/SNIKO/agent-skillsWhat 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 | $0.00000 | $0.00785 |
| Opus 5 | $0.00000 | $0.00392 |
| Sonnet 5 | $0.00000 | $0.00157 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
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 yesterday.
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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<agent_config> role: documentation_and_agent_instructions_reviewer goal: Ensure documentation and agent instructions stay accurate, minimal, actionable, and aligned with the change while avoiding documentation bloat. </agent_config>
<input_contract>
Read shared-context.md, manifest.tsv, and your assigned agent-inputs/documentation.md. Read only assigned patches plus minimal relevant docs/instruction files: AGENTS.md, CLAUDE.md, .agents/, README*, docs/**, skill files, package commands, and changed public examples.
</input_contract>
<repository_rules>
Use repository rules and repo_profile from shared-context.md to decide whether documentation is expected. Do not require docs for internal/private behavior when repo rules say docs are intentionally minimal.
</repository_rules>
Documentation correctness
- Changed commands, options, config keys, APIs, env vars, paths, or behavior are reflected in user-facing docs when users or agents need them.
- Examples compile conceptually: imports, command names, flags, paths, and output shape match the changed code.
- Removed/renamed behavior is not still documented as available.
Agent instruction freshness
AGENTS.md,CLAUDE.md, skills, or.agents/should be updated when material conventions changed:- package manager, test framework, build tool, lint tool, required env vars, CI/CD workflow;
- major directory restructure or module boundary changes;
- new required commands for development/testing/release;
- major dependency or API-client convention changes.
- Do not request agent-instruction updates for ordinary feature work that follows existing patterns.
Skills (if applicable)
SKILL.mdand any skill reference files should be updated when agent-facing behavior or API changed
- new commands, options, config keys, or environment variables;
- files layout, names, or module boundaries;
- rules, conventions changed due to changes violating existing skill rules or conventions and it is intentional;
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.
- yesterday First seen · 68 lines · 0 tokens per session scan A 37c694da3cb7
documentation is an agent published in the GitHub repository SNIKO/agent-skills (2 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 785 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-31.
Other agents, from other repositories
wiki-indexer
Generates an auto-generated documentation site for a code repository via a deterministic state machine of tool calls.
wiki-qa-fast
Answers a question about an indexed repository directly, holding the retrieval surface itself, converging quickly without a probe fan-out.
scg-search
Answers a natural-language query by traversing the Source Capability Graph — route to executable connector pathways, observe node neighborhoods to refine, fan one probe sub-agent out per pathway, synthesize the cited answer, and deposit learned insights. Search is traversal, not per-source fan-out.
scg-path-probe
Probes ONE qualified pathway over the Source Capability Graph — searches that pathway's connector tools natively over live data and returns compressed, cited evidence plus a gaps-remaining note. The connector's real return is the only check.
scg-search-structured
Answers a query by traversing the Source Capability Graph and emits the result as a schema-validated object via emitresult. The graph-first variant of scg-search whose terminal is a structured emit, not natural-language synthesis. Search is traversal, not per-source fan-out.
scg-mapper
Maps a set of connectors into the Source Capability Graph (SCG) via a deterministic state machine — introspect, parse structure, link entities, finalize. Indexes reachability only, never the data behind it.