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.
git clone --depth 1 https://github.com/justinjdev/fellowshipWrote 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/commands/justinjdev/fellowship/validate-docs)<a href="https://agentmods.dev/commands/justinjdev/fellowship/validate-docs"><img src="https://agentmods.dev/badge/commands/justinjdev/fellowship/validate-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/commands/justinjdev/fellowship/validate-docs"><img src="https://agentmods.dev/badge/commands/justinjdev/fellowship/validate-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.00018 | $0.01171 |
| Opus 5.5 | $0.00007 | $0.00468 |
| Sonnet 5.5 | $0.00004 | $0.00234 |
| Haiku 4.5 | $0.00002 | $0.00117 |
Grade A, and why
validate-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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Docs
Layout assumption: This skill expects the standard fellowship layout — site at
site/src/routes/, plugin atplugin/. If your project uses a different structure, the path checks below will not match.
Overview
Checks that documentation is current against the codebase: the site changelog, README changelog, skills/commands page, agents page, marketplace description, and config schema. Collects all findings across Steps 1–6, then emits a single structured report in Step 7. Does not modify any files — report-only.
Process
Step 1: Changelog (site)
Read site/src/routes/changelog/+page.svelte. If the file does not exist, flag it as missing and continue to Step 2.
- If there is an
<!-- unreleased -->section, flag it: changelog has unreleased changes that need a version. - If there is no unreleased section, check commits since the last tag:
Ifgit log $(git describe --tags --abbrev=0)..HEAD --oneline --no-mergesgit describe --tags --abbrev=0fails (no tags exist), skip the commit comparison and note "no tags found." Otherwise, if there are feat/fix commits not reflected in the changelog, flag it.
Step 2: Changelog (README)
Read README.md and find the ## Changelog section. If README.md does not exist, flag it as missing and continue to Step 3.
Check commits since the last tag:
git log $(git describe --tags --abbrev=0)..HEAD --oneline --no-merges
If git describe --tags --abbrev=0 fails (no tags exist), skip the commit comparison and note "no tags found." Otherwise, if there are feat/fix commits not covered by the latest README changelog entry, flag it.
Step 3: Skills and commands page
Read site/src/routes/skills/+page.svelte. If the file does not exist, flag it as missing and continue to Step 4.
List all skills in plugin/skills/*/SKILL.md and all commands in plugin/commands/*.md. Cross-reference against what's documented on the skills page. Flag any that are present in the plugin but missing from the page.
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 · 112 lines · 18 tokens per session scan A e1c37aee65ef
validate-docs is a command published in the GitHub repository justinjdev/fellowship (5 stars, last pushed 17d ago), licensed Apache-2.0. It adds 18 tokens to every session and 1,171 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 commands, from other repositories
auto-mode
Idea-to-running-code lifecycle orchestration. 10-phase pipeline with 5 hard decision gates, wave-based parallelism, and STATE.json resumability. Composes /deep-research, /auto-swarm-nth, /production-upgrade, /security-audit, and /ship into a single end-to-end flow.
max-research
Nuclear-scale autonomous research — deploys 500-1000 agents in ONE massive simultaneous wave for exhaustive topic saturation. Deep-research methodology × auto-swarm scale = maximum parallel intelligence. WARNING: Extreme resource consumption.
omni-plan
ProductionOS flagship — 13-step orchestrative pipeline with tri-tiered evaluation, recursive convergence, CEO/Eng/Design review chain, CLEAR framework evaluation, multi-model judge tribunal, and autonomous PIVOT/REFINE/PROCEED decisions. Targets 100% production-ready output.
auto-swarm-nth
Nth-iteration agent swarm — spawns parallel agent waves, evaluates strictly per wave, re-swarms gaps until 100% coverage and 10/10 quality. Can invoke any ProductionOS skill or command within waves.
frontend-upgrade
Full-stack frontend upgrade pipeline — fuses /production-upgrade iterative audit with /plan-ceo-review vision and /plan-eng-review rigor. Deploys parallel auto-swarm agents for iterative audit and execution. Enriched with /deep-research for competitive parity.
omni-plan-nth
Nth-iteration omni-plan — recursive orchestration that chains ALL ProductionOS skills and agents, evaluates strictly per iteration, and loops until 10/10 is achieved. Each iteration can invoke any command or skill in the system.