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/Floka-as/floka-marketplaceWrote 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/floka-as/floka-marketplace/audit)<a href="https://agentmods.dev/commands/floka-as/floka-marketplace/audit"><img src="https://agentmods.dev/badge/commands/floka-as/floka-marketplace/audit/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/floka-as/floka-marketplace/audit"><img src="https://agentmods.dev/badge/commands/floka-as/floka-marketplace/audit.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.00047 | $0.01586 |
| Opus 5 | $0.00023 | $0.00793 |
| Sonnet 5 | $0.00009 | $0.00317 |
| Haiku 4.5 | $0.00005 | $0.00159 |
Grade A, and why
audit 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 11d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Output is a structured report with ✅ / ⚠️ / ❌ verdicts and concrete suggestions. The audit is advisory — it doesn't modify the file unless the user explicitly asks for fixes.
Step 1: Locate and read the board
Check for .claude/board.md then ~/.claude/board.md. If neither exists, stop and tell the user to run /board:build first.
Parse the board:
- Pipeline stage assignments
- Free agents
- Each member's entry: domain, frameworks, when to invoke, won't help with, characteristic questions, counterweight-to mapping
Step 2: Run five audit checks
Check A — Pipeline coverage
Of the 8 canonical stages (POSITION, BUILD, SUSTAIN, SELL, GROW, DISTRIBUTE, SYSTEMATIZE, SHIP IT), which are filled?
- ✅ All 8 stages have an advisor (or the user has explicitly removed/merged stages and the remainder are filled)
- ⚠️ 1–2 unfilled stages (often acceptable for solo / early-stage)
- ❌ 3+ unfilled stages — the board can't carry a
/board:pipelinerun
For each unfilled stage, suggest 2–3 archetypes that would fit (operators, founder-types, or "any [domain] expert").
Check B — Voice distinctness
Compare each pair of advisors. Are their entries genuinely different, or do their Frameworks and When to invoke sections substantially overlap?
- ✅ Each advisor has a clearly distinct voice and domain
- ⚠️ 2 advisors with significant overlap — risk of redundancy in
/board:meeting - ❌ 3+ pairs overlap — the board is collapsing into a single chorus
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.
- 11d ago First seen · 160 lines · 47 tokens per session scan A d8f119435158
audit is a command published in the GitHub repository Floka-as/floka-marketplace (7 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 1,586 once invoked, about $0.0002 per session on Opus 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.