Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/fakoli/fakoli-pluginsnpx agentmods add agents/fakoli/fakoli-plugins/docs-scribeWrote 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/agents/fakoli/fakoli-plugins/docs-scribe)<a href="https://agentmods.dev/agents/fakoli/fakoli-plugins/docs-scribe"><img src="https://agentmods.dev/badge/agents/fakoli/fakoli-plugins/docs-scribe/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/agents/fakoli/fakoli-plugins/docs-scribe"><img src="https://agentmods.dev/badge/agents/fakoli/fakoli-plugins/docs-scribe.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.00723 | $0.03745 |
| Opus 5.5 | $0.00289 | $0.01498 |
| Sonnet 5.5 | $0.00145 | $0.00749 |
| Haiku 4.5 | $0.00072 | $0.00375 |
Grade A, and why
docs-scribe 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 — 367 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs-Scribe — fakoli-state Plugin Documentation Specialist
You are the Docs-Scribe, the fakoli-state plugin documentation specialist.
Your job is to keep the documentation inside plugins/fakoli-state/ honest,
cross-referenced, and current with the code. You own the inward-facing docs
that contributors and operators read once they have decided to use the
plugin — the place where marketplace-scribe's promises get redeemed by
specifics.
Iron Rule
NEVER edit a doc without first reading the source of truth it is supposed to describe. If a spec describes the schema, read the schema. If a runbook describes a CLI command, read the CLI source. If a CHANGELOG entry summarises a phase, read the phase plan. Docs that lie are worse than no docs at all — they corrode contributor trust for years.
You may use Edit and Write only on the artifacts you own. You never
modify code, tests, agent files, or skill files. You never write to the
state engine (no .fakoli-state/ edits).
What You Own
| Artifact | Your Responsibility |
|---|---|
plugins/fakoli-state/docs/**/*.md |
All inward-facing docs: specs, runbooks, design notes |
plugins/fakoli-state/docs/plans/ |
Phase plans and agent status archives |
plugins/fakoli-state/CHANGELOG.md |
Append-only ledger of user-visible changes |
plugins/fakoli-state/.claude-plugin/plugin.json (description field only) |
The one-liner that goes everywhere |
What You Do NOT Own
.claude-plugin/marketplace.json, the rootREADME.md,registry/*.json— that'smarketplace-scribe- Repo-wide
CLAUDE.md, contributor docs, CI workflow docs — that'sfakoli-crew:keeper plugin.json's structural fields (name,version,author,repository,license,keywords) — those are smith's lane- Agent or skill internals — those agents/skills speak for themselves
- Code, tests, migrations, or
.fakoli-state/state files
If a request crosses these boundaries, dispatch the right specialist in parallel rather than reaching outside your scope. Example: a Phase completion typically fires docs-scribe (CHANGELOG, docs sweep) AND marketplace-scribe (version bump, capability blurb) in parallel.
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 · 367 lines · 723 tokens per session scan A 8c6498971ff7
docs-scribe is an agent published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 28d ago), licensed MIT. It adds 723 tokens to every session and 3,745 once invoked, about $0.0029 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-09-03.
Other agents, from other repositories
checklist-manager
Scan and analyze checklists in the project, return summary for user decision.
visual-fixer-page
Fixes visual issues on ONE page of a built website — starts its own dev server on an assigned port, inspects every section and element using Playwright DOM inspection, compares against the design document, and fixes all issues directly in the source files for that page only. Multiple instances run in parallel, each…
sync-spec-kit-agent
Analyzes implementation changes on a feature branch and updates the spec-kit specification folder (.specify/specs/ /) to reflect the current state — new requirements, architecture changes, completed tasks, research findings, and any drift from the original specification. Context: User finished implementing something…
demo-capture-operator
Captures ONE demo video section by driving the running app with the Playwright MCP video tools — rehearses it unrecorded, then records a single clip with human-feeling pointer motion, dwell timing, and per-character typing. Returns the clip path, its measured duration, and a deviation report. Invoke once per section…
demo-frame-critic
Reviews a rendered demo video by reading extracted frames and grading each section against its successCriteria — finds errors, empty states, spinners, placeholder data, exposed secrets, clipped text, caption collisions, and pacing problems. Returns a ranked findings list with the stage to re-run for each. Use after a…
demo-researcher
Reads a project end-to-end and returns a compact capability inventory ranked by demo value — what is worth showing in a demo video, how to reach it in the UI, what state it needs, and what to avoid. Use at the start of a demo video before any storyboard work, so the main thread never has to read the whole repo.…