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 backchainai/backchain-plugins --skill docsgit clone --depth 1 https://github.com/backchainai/backchain-pluginsWrote 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/backchainai/backchain-plugins/docs)<a href="https://agentmods.dev/skills/backchainai/backchain-plugins/docs"><img src="https://agentmods.dev/badge/skills/backchainai/backchain-plugins/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.
<a href="https://agentmods.dev/skills/backchainai/backchain-plugins/docs"><img src="https://agentmods.dev/badge/skills/backchainai/backchain-plugins/docs.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.00173 | $0.03914 |
| Opus 5.5 | $0.00069 | $0.01566 |
| Sonnet 5.5 | $0.00035 | $0.00783 |
| Haiku 4.5 | $0.00017 | $0.00391 |
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 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs
Route one document to the mode it belongs in, write it under that mode's constraints, then check its markdown form.
The unit of work is one document and one next action. This skill does not plan a documentation set top-down, does not audit a whole docs/ tree in one pass, and does not produce an outline for a future set of pages.
Two paths share the same routing step: writing a new document (the write path) and assessing one that already exists (the place path). Both start at the compass below, and both end at the same markdown-form check.
Where this does not apply
Diataxis governs product documentation written for a user. It does not govern everything that happens to be a markdown file in a repository.
Check the request against this table before routing anything:
| Out of scope | Why |
|---|---|
| ADRs and decision records | A dated historical artifact, not one of the four modes |
| Commit messages, PR descriptions | Not user documentation |
| Changelogs, release notes | Chronological by nature; no mode applies |
| Code comments and docstrings | Belong to the code, not the documentation set |
CLAUDE.md, agent and tool config |
Instructions to a machine, not a user |
When the request names one of these, say which row applies and stop before opening the compass.
None of the four modes fits an artifact that is fundamentally dated, historical, or machine-facing.
READMEs are in scope: advise on README structure when asked (trim it, reorder it, link out more aggressively), but never propose extracting its parts into separate mode documents the way this skill would for a contaminated tutorial or how-to guide. A README is a landing page and legitimately hybrid.
When scope is ambiguous
- A design doc that reads like project history belongs with ADRs, even if nobody labeled it one.
- A "docs" folder that turns out to hold internal runbooks for the team, not instructions for a product user, is out of scope until the request is reframed around an external reader.
- A file named
NOTES.mdsitting next to code is closer to a code comment than to any of the four modes; ask what reader it serves before routing it.
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- evals/evals.json 16 KB
- evals/trigger-evals.json 4.9 KB
- references/commonmark.md 8.4 KB
- references/explanation.md 5.6 KB
- references/frontmatter.md 5.0 KB
- references/how-to.md 5.5 KB
- references/reference.md 5.6 KB
- references/tutorial.md 6.0 KB
- scripts/check_markdown.py 29 KB runs code
- scripts/fixtures/clean-fenced.md 1.0 KB
- scripts/fixtures/malformed.md 684 B
- scripts/test_check_markdown.py 35 KB runs code
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 First seen · 253 lines · 173 tokens per session scan A ec86b859aa22
docs is a skill published in the GitHub repository backchainai/backchain-plugins (4 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 173 tokens to every session and 3,914 once invoked, about $0.0007 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
mnemon
Persistent memory CLI for LLM agents. Store facts, recall past knowledge, link related memories, manage lifecycle.
mnemon
Persistent memory for MiniMax Code. Recall durable context, store important facts and decisions, and link related memories with the mnemon CLI.
evolve-lite:save-trajectory
Save the current conversation as a trajectory JSON file in OpenAI chat completion format for analysis and fine-tuning.
alive:demo
Generate a believable, lived-in ALIVE world from a free-text persona description (custom path) or a deterministic sandbox preset. Routes the create/list/activate/deactivate/delete/status surface and orchestrates the 5-stage subagent generation pipeline.
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
triage
Triages a PR comment — from a bot (Copilot, CI) or a human reviewer. Routes to the triagehelper.py helper for identity checks, thread snapshotting, isolated-worktree fixes, and publish/reply/resolve mechanics; you classify the finding and apply a justified fix. --dry-run is fully read-only (investigation and a printed…