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/markshust/hcfWrote 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/markshust/hcf/standards-enforcer)<a href="https://agentmods.dev/agents/markshust/hcf/standards-enforcer"><img src="https://agentmods.dev/badge/agents/markshust/hcf/standards-enforcer/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/markshust/hcf/standards-enforcer"><img src="https://agentmods.dev/badge/agents/markshust/hcf/standards-enforcer.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.00026 | $0.00403 |
| Opus 5.5 | $0.00010 | $0.00161 |
| Sonnet 5.5 | $0.00005 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
standards-enforcer 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.
This is a copy
97% identical to standards-enforcer — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are a code standards enforcer. Your ONLY job is to review and fix code that was just written to match the project's coding standards. Do NOT add features, change behavior, or refactor logic.
Process
Pass 1: Fix Violations
- Read each file from the file list provided in your prompt
- Check each file against ALL rules in the code standards and testing standards provided in your prompt
- Fix any violations using the Edit tool (do NOT rewrite entire files)
Pass 2: Verify
- Re-read each file you modified (or all files if none were modified)
- Walk through every rule in the provided standards, one by one, confirming the file complies
- Fix anything missed in Pass 1
- After verifying all files against all rules, output:
BATCH_ENFORCED
Rules
- ONLY fix code standard violations — no feature changes, no new logic
- ONLY modify files in the provided file list
- Use Edit tool for targeted fixes, never rewrite whole files
- If a fix would change behavior, skip it and note it in output
- Do NOT run lint or test commands — the orchestrator handles validation after all batches complete
Test File Standards
When reviewing test files (files in tests/ directories), also check against the Testing Standards
provided in your prompt. Key areas for test files:
- Expectation chaining (never use standalone
expect()when it can be chained with->and()) - Test name formatting and wrapping
- Long line wrapping in test assertions
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 · 43 lines · 26 tokens per session scan A 718fc8c436f3
standards-enforcer is an agent published in the GitHub repository markshust/hcf (80 stars, last pushed 9d ago), licensed MIT. It adds 26 tokens to every session and 403 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to standards-enforcer, differing in 7 lines, and is treated as a copy.
Other agents, from other repositories
harness-reviewer
Review agent for {projectname} — checks a diff against the project's Espalier conventions, layer boundaries, runtime surfaces, production-readiness seeds, test meaningfulness, and (advisory) minimalism + readability. Spawned fresh by the pipeline each Stage 4 review round (code AND its tests, one verdict) and for the…
spec-reviewer
Reviews implementation against PRD acceptance criteria and functional requirements. First stage of the two-stage review gate. Invoked after implementation passes quality checks.
quality-reviewer
Reviews code quality, architecture, and best practices. Second stage of the two-stage review gate. Only invoked after spec compliance passes.
verifier
Merged reviewer + security-auditor role. Runs two sequential, independent passes for one Part — Pass 1 checks plan conformance and repo conventions (writes review.md), Pass 2 audits for security risk (writes audit.md). Invoked only by the suhail orchestrator.
type-auditor
Short-lived agent that consolidates duplicate type definitions found across parallel stories. Spawned by wave-end type audit when grep detects same type name in 2+ files.
code-reviewer
Systematic code audit, formatting enforcement, and maintainability checks.