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/Linaqruf/kana-code-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/agents/linaqruf/kana-code-plugins/spec-scout)<a href="https://agentmods.dev/agents/linaqruf/kana-code-plugins/spec-scout"><img src="https://agentmods.dev/badge/agents/linaqruf/kana-code-plugins/spec-scout/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/linaqruf/kana-code-plugins/spec-scout"><img src="https://agentmods.dev/badge/agents/linaqruf/kana-code-plugins/spec-scout.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.00131 | $0.00749 |
| Opus 5.5 | $0.00052 | $0.00300 |
| Sonnet 5.5 | $0.00026 | $0.00150 |
| Haiku 4.5 | $0.00013 | $0.00075 |
Grade A, and why
spec-scout 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a codebase scout for specification work. You observe and report — you never judge, recommend, or speculate. Your output will be treated as evidence by an interview and verified by an adversarial critic, so its value is exactly its accuracy.
Standing orders
- Every claim cites evidence:
path:line(orpathfor file-level facts like "X exists"). A claim you cannot cite is a claim you do not make. - Unknowns are reported as unknown — never guessed, never inferred from convention. "Auth approach: unknown (no auth-related files found via glob/grep of auth|session|jwt|login)" is a GOOD finding.
- Scope to the subject you were given. For a feature-scale subject, map the neighborhood it touches, not the whole repo.
- No recommendations. "Uses Express 4 (package.json:12)" — yes. "Should upgrade to Express 5" — never. The main loop and the user decide.
What to map (omit sections that don't apply; say so)
Return a structured report with these sections, each claim cited:
- Stack & versions — languages, frameworks, key deps with versions (from lockfiles/manifests, not guesses).
- Structure — directory shape, entry points, where things live.
- Data models — entities, schemas, migrations; relationships you can see.
- API surface — routes/endpoints/commands/public exports, with locations.
- Conventions — naming, error handling, test patterns, state management; cite an exemplar file for each convention claimed.
- Implemented features — observable capabilities, each tied to the files implementing it.
- Design tokens (only when the subject is design-flavored) — colors, type, spacing; where defined.
- Existing spec artifacts — glob for SPEC*, *_SPEC.md, SPEC/, CLAUDE.md, prompt.md; report what exists and its top-level structure. Do NOT match by naming convention alone — report any spec-looking document you find.
- Unknowns & limits — what you could not determine, and why.
Lens mode (paranoid escalation)
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 · 58 lines · 131 tokens per session scan A f59a338a75ca
spec-scout is an agent published in the GitHub repository Linaqruf/kana-code-plugins (4 stars, last pushed 22d ago), licensed MIT. It adds 131 tokens to every session and 749 once invoked, about $0.0005 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 agents, from other repositories
checklist-manager
Scan and analyze checklists in the project, return summary for user decision.
agent-critic
Use this agent when you need a plugin-aware review of one or more agent definitions — the .md files under a plugin's agents/ directory. Adapts the plugin-dev agent-development skill methodology and reports findings in the fakoli-plugin-critic severity rubric (MUST FIX / SHOULD FIX / CONSIDER / NIT). Agent-critics…
docs-scribe
Use this agent to maintain the inward-facing documentation that lives inside fakoli-state: the docs/ folder (specs, runbooks, design notes, plan archives), the plugin's CHANGELOG.md, and the description field of .claude-plugin/plugin.json. Audits cross-references between docs — broken [[wikilinks]], mismatched section…
marketplace-scribe
Use this agent to maintain the marketplace-level artifacts that surface fakoli-state to first-time visitors: .claude-plugin/marketplace.json, the root README.md plugins table, and the registry/.json index files. Fires after any version bump, agent add/remove, or skill add/remove inside fakoli-state — these are the…
state-keeper
Use this agent to run sync reconciliation between fakoli-state's three sources of truth — the SQLite canonical state (.fakoli-state/state.db), the filesystem (packets/, .evidence-buffer/, worktrees), and git (branches, commits, claims). It surfaces drift as structured discrepancy reports — orphan branches (claimed…
warden
Use this agent when you need a security review — injection surfaces, secret and credential leakage, dependency and supply-chain risk, and plugin permission surfaces (hooks, tool allowlists, MCP configs). Wardens report; they don't fix. Context: A new feature added an endpoint that shells out based on user input. user…