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/markshust/hcf/standards-enforcergit clone --depth 1 https://github.com/markshust/hcfWhat 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.00026 | $0.00403 |
| Opus 5 | $0.00013 | $0.00201 |
| Sonnet 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 2d 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.
- 2d ago First seen · 43 lines · 26 tokens per session scan A 718fc8c436f3
standards-enforcer is an agent published in the GitHub repository markshust/hcf (67 stars, last pushed 7d ago), licensed MIT. It adds 26 tokens to every session and 403 once invoked, about $0.0001 per session on Opus 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
seo-drift
SEO drift analysis agent. Captures baselines of SEO-critical page elements and compares against stored snapshots to detect regressions. Reports changes with severity classification. Only spawned when a drift baseline exists for the URL.
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
audit-creative
Cross-platform creative specialist. Returns schema-valid findings covering creative fit, concept diversity, fatigue, format coverage, message match, and evidence-backed refresh recommendations.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
nodejs-expert
Specializes in Node.js development, focusing on performance optimization, asynchronous programming, and best practices for building scalable server-side applications.