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.
npx skills add chan4lk/specclaw --skill bf-statusgit clone --depth 1 https://github.com/chan4lk/specclawWrote 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/chan4lk/specclaw/bf-status)<a href="https://agentmods.dev/skills/chan4lk/specclaw/bf-status"><img src="https://agentmods.dev/badge/skills/chan4lk/specclaw/bf-status/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/chan4lk/specclaw/bf-status"><img src="https://agentmods.dev/badge/skills/chan4lk/specclaw/bf-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00148 | $0.01427 |
| Opus 5 | $0.00074 | $0.00714 |
| Sonnet 5 | $0.00030 | $0.00285 |
| Haiku 4.5 | $0.00015 | $0.00143 |
Grade A, and why
bf-status 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 3d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
specclaw bf-status
First, run specclaw-ensure-init .specclaw — idempotently creates .specclaw/ if it doesn't exist (silent if already initialized; auto-inits using the current directory's basename as the project name).
Show where the brownfield workstream stands. Read-only side-command — no specclaw-validate-change call, no <change> involved, matching the status/patterns/bf-analyze pattern.
-
Compute and render:
specclaw-bf-status .specclawDeterministic, read-only, cheap. Everything it reports is recomputed from each phase's own declared artifacts on every run.
If it exits non-zero, surface its stderr message verbatim and stop — the only failures are a missing
<specclaw_dir>(run/specclaw:init) and a missing argument. Don't retry, don't guess a different path. -
Relay its output to the user. It is already a finished markdown report — a phase table, a Needs attention list, and a Next line. Present it as-is rather than paraphrasing it into prose. The attention list in particular is a work list someone can act on today; summarising it away is exactly the failure this command exists to fix.
-
Lead with the
Nextline, then name anything in Needs attention the user should know is human work no command can do for them: answering a blocking question, capturing a fixture or a screenshot, confirming the module map. Those are the items that silently stall a rebuild, because no command ever fails on account of them. -
If the user asked about one specific module rather than the workstream as a whole, run the per-module view instead — it answers a different question and this command deliberately does not duplicate it:
specclaw-bf-rebuild-collect module-status .specclawThat writes
.specclaw/analysis/module-status.md: one row perMOD-###with backlog items planned/total, scenarios captured/designed, the latest module-scoped replay verdict, stub-tainted item counts, and open questions naming that module.
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.
- 3d ago First seen · 61 lines · 148 tokens per session scan A 281007718501
bf-status is a skill published in the GitHub repository chan4lk/specclaw (12 stars, last pushed 4d ago), licensed MIT. It adds 148 tokens to every session and 1,427 once invoked, about $0.0007 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-09-05.
Other skills, from other repositories
raise-issue
Turns "this is broken" into a well-formed issue in the team's tracker, written in the codebase's own vocabulary. Built for someone who uses the product and does not read code — it asks a few plain-English questions, works out for itself which part of the code they are describing, checks whether the same thing has…
report-issue
Alias for the raise-issue skill. Turns "this is broken" into a well-formed issue in the team's tracker, written in the codebase's own vocabulary — a few plain-English questions, a check of which part of the code is being described, a duplicate check, then filing it once the person says yes. Built for someone who uses…
capture-lessons
Ship and capture lessons workflow. Creates the PR, updates lessons learned, updates documentation, generates the sprint retrospective, and updates the backlog. Use at the end of a sprint cycle, or when the user says "ship", "capture", "lessons", "retro", "retrospective", "wrap up", or "done with this sprint". Also use…
sprint-plan
Sprint planning workflow. Creates a structured plan from the backlog with tasks, acceptance criteria, dependencies, and risks. Use when starting a new sprint, planning work, or when the user says "plan", "sprint", "what should we work on", or "next sprint". Always use this skill to start a sprint cycle — never plan…
update-briefs
Updates the briefs/ shared memory directory after a sprint completes. Reads sprint outputs and writes structured summaries for other agents. Use after any sprint completes, or when the user says "update briefs", "sync state", "update project state", or "what changed". Also use automatically after /capture-lessons or…
project-launch-checklist
Audits a project for hiring visibility before going public. Verifies README clarity for impatient hiring managers, checks evaluation setup, tests, CI/CD, config file, and deployment link. Generates a pre-launch audit report with gaps and priorities. Use when you're ready to make a project visible to hiring managers or…