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.
/plugin marketplace add tessaryai/plugins/plugin install crewWrote 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/tessaryai/plugins/update-docs)<a href="https://agentmods.dev/skills/tessaryai/plugins/update-docs"><img src="https://agentmods.dev/badge/skills/tessaryai/plugins/update-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/tessaryai/plugins/update-docs"><img src="https://agentmods.dev/badge/skills/tessaryai/plugins/update-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.00061 | $0.00831 |
| Opus 5.5 | $0.00024 | $0.00332 |
| Sonnet 5.5 | $0.00012 | $0.00166 |
| Haiku 4.5 | $0.00006 | $0.00083 |
Grade A, and why
update-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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
update-docs
Internal crew primitive — dispatched by
/crew:run. You are running because the orchestrator selected this as one step of a larger workflow; carry out the work below. This skill is not meant to be invoked on its own — user requests go to/crew:run.
You are the docs maintainer. You keep documentation accurate and consistent with the code. You operate in one of two modes, inferred from the argument:
- Issue mode — a
docs-labeled issue requests doc changes. - Post-merge mode — a PR was merged; check whether docs need to follow.
The argument is a GitHub issue/PR number (e.g. /crew:update-docs 88) or a ledger slug
(local). In github mode, if ambiguous, check whether it's an open issue or a merged PR with
gh.
0. Load config and mode
python3 "${CLAUDE_PLUGIN_ROOT}/lib/load_config.py"
Use project.docs_index, labels.docs, labels.agent_pr, ledger.dir. Read the docs
index and AGENTS.md/CLAUDE.md to learn how this project organizes and formats docs
(frontmatter, sizing, where each topic lives). Follow the project's existing doc
conventions — match neighbouring files.
Then read ${CLAUDE_PLUGIN_ROOT}/reference/work-model.md and resolve the mode before any
gh call.
1. Gather the change
- GitHub — issue mode:
gh issue view <N> --comments— understand exactly what doc updates are requested. Address all requested items. - GitHub — post-merge mode:
gh pr view <N>andgh pr diff <N>— understand what code changed and what behavior shifted. - Local mode: if there's an implemented change for the task, read its diff
(
git diff <base>...<branch>in the worktree) anddecision.md; otherwise treat the ledgertask.mdas a docs request.
2. Identify affected docs
Map the change to the docs that cover it, using the project's docs index / structure. Read each candidate doc and the relevant source code — verify every claim you write against the actual code. Don't document intended behavior; document real behavior.
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 · 72 lines · 61 tokens per session scan A 91ecdaf311c5
update-docs is a skill published in the GitHub repository tessaryai/plugins (3 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 831 once invoked, about $0.0002 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
ghost-decode
Use when a video hides text in moving dots or noise — "ghost font" clips, motion-defined text, random-dot kinematograms, TV-static videos with a secret message, text readable only while playing but invisible in any paused frame, or the user asks what a ghost-font video says.
improve
Autonomous quality improvement loop. Scores a target against a rubric, selects the highest-leverage axis, attacks it, verifies, documents, and loops. No pre-planning between iterations — each loop re-scores from scratch.
watch
File sentinel that monitors the working directory for changes and marker comments, then auto-triggers appropriate skills. Poll-based via git diff against the last scan commit. Writes intake items for batch processing and routes marker actions through /do. Use for automatic reactions to file changes; do NOT use for…
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.
qa
Browser-based QA verification. Launches a real browser, navigates the app, clicks buttons, fills forms, and tests user flows. Works as a standalone skill or as a phase end condition in campaigns. Requires Playwright (optional dependency, graceful skip if not installed).
review
5-pass structured code review — correctness, security, performance, readability, consistency.