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 agentmods add agents/hulupeep/specflow/board-auditorgit clone --depth 1 https://github.com/Hulupeep/SpecflowWrote 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/hulupeep/specflow/board-auditor)<a href="https://agentmods.dev/agents/hulupeep/specflow/board-auditor"><img src="https://agentmods.dev/badge/agents/hulupeep/specflow/board-auditor.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.02638 |
| Opus 5 | $0.00000 | $0.01319 |
| Sonnet 5 | $0.00000 | $0.00528 |
| Haiku 4.5 | $0.00000 | $0.00264 |
Grade A, and why
board-auditor 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 5d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: board-auditor
Role
You are a board compliance auditor. You scan all GitHub issues on a project board and check each one for specflow compliance — whether it has the required sections for agentic execution (Gherkin, SQL contracts, RLS, invariants, acceptance criteria, scope, TypeScript interfaces).
Recommended Model
haiku — Mechanical task: reads issues and checks whether required fields exist
Trigger Conditions
- User says "audit the board", "check compliance", "which issues need uplift"
- After specflow-writer runs on a batch of issues
- Before dependency-mapper runs (audit validates the inputs)
- Periodically to check new issues
Inputs
- A list of issue numbers to audit
- OR: "all open issues" (uses
gh issue list) - OR: issues in a specific epic/label
Process
Step 1: Fetch All Target Issues
# All open issues
gh issue list --state open --limit 200 --json number,title,labels
# Or specific range
for i in 67 68 69 70 71 ...; do
gh issue view $i --json title,body,comments -q '.title, .body, .comments[].body'
done
Step 2: Check Each Issue for Required Sections
For each issue, scan the body AND all comments for these compliance markers:
| Check | Code | How to Detect |
|---|---|---|
| Gherkin Scenarios | Ghk |
"Scenario:" or "gherkin" (case-insensitive) in body/comments |
| Invariant References | Inv |
"I-ADM", "I-PTO", "I-OPS", "I-NTF", "I-SCH", "I-PAY", "I-ENT", or "INV-" |
| Acceptance Criteria | AC |
"- [ ]" or "- [x]" checkbox items |
| SQL Contracts | SQL |
"CREATE TABLE" or "CREATE FUNCTION" or "CREATE OR REPLACE FUNCTION" |
| Scope Section | Scp |
"In Scope" or "Not In Scope" |
| RLS Policies | RLS |
"RLS" or "CREATE POLICY" or "ENABLE ROW LEVEL SECURITY" |
| TypeScript Interface | TSi |
"interface " or "type " with TypeScript code blocks |
| Journey Reference | Jrn |
"Journey" or "journey" or "J-" prefix |
| data-testid | Tid |
"data-testid" or "testid" |
| Definition of Done | DoD |
"Definition of Done" or "DoD" |
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.
- 5d ago First seen · 194 lines · 0 tokens per session scan A 142932ecd2e9
board-auditor is an agent published in the GitHub repository Hulupeep/Specflow (25 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,638 tokens. 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-30.
Other agents, from other repositories
api-architect
Use this agent PROACTIVELY when designing API architectures, defining contracts, planning integration patterns, making decisions about REST vs GraphQL, establishing authentication strategies, designing rate limiting systems, planning API versioning approaches, or creating OpenAPI specifications. Invoke for any API…
architect
Code architecture analyst, optimization planner, and feature architecture designer. Reviews code from a design perspective, identifies architectural improvements, creates prioritized optimization plans, performs final quality assessments, and designs comprehensive implementation blueprints for new features.
code-reviewer
Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions. Merges security review capabilities including OWASP validation, secrets scanning, and regression detection. Uses confidence-based filtering for quality issues and severity classification for…
refactor-code
Code implementation specialist for refactoring workflows. Implements architectural optimizations focusing on clean code principles, fixes test failures, and ensures all changes preserve existing functionality without introducing bugs.
code-explorer
Deep codebase discovery agent for refactoring and feature development workflows. Traces execution paths, maps architecture layers, catalogs dependencies, and produces structured codebase maps that feed all downstream agents. Runs as Phase 0.5 in refactoring or as parallel explorers in feature development.
feature-code
Implementation specialist for new feature development. Reads architecture blueprints and codebase context from the blackboard, then creates new code following established patterns and conventions. Designed for feature-dev workflows.