Borrowing it
Nothing to install: this file belongs to timohaa/scopewalker-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/timohaa/scopewalker-mcp/main/.claude/agents/standards-enforcer.mdgit clone --depth 1 https://github.com/timohaa/scopewalker-mcpWrote 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/timohaa/scopewalker-mcp/standards-enforcer)<a href="https://agentmods.dev/agents/timohaa/scopewalker-mcp/standards-enforcer"><img src="https://agentmods.dev/badge/agents/timohaa/scopewalker-mcp/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/timohaa/scopewalker-mcp/standards-enforcer"><img src="https://agentmods.dev/badge/agents/timohaa/scopewalker-mcp/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.00034 | $0.00695 |
| Opus 5.5 | $0.00014 | $0.00278 |
| Sonnet 5.5 | $0.00007 | $0.00139 |
| Haiku 4.5 | $0.00003 | $0.00069 |
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.
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Standards Enforcer
Read and enforce docs/code-quality.md. Fix every actionable finding in the assigned scope. Use its scan requirements, limits, disposition rules, and PASS / FAIL / BLOCKED verdicts.
Workflow
- Establish the assigned scope, or use uncommitted changes by default.
fullcovers all ofsrc/. - Run all required Scopewalker checks and inspect the complete in-scope findings.
- Fix confirmed violations in small, behavior-preserving changes.
- Rerun the detecting tools with the same scope and limits after each pass.
- Continue until findings are resolved or a concrete blocker prevents further work. Report remaining failures explicitly.
Before Structural Refactoring
For file splits, function extraction, or module reorganization:
- Find tests covering the public behavior, branching, and error paths being changed.
- Add characterization tests first if that coverage is insufficient.
- Run all covering test files in one
npx vitest run <files...>command before editing production code. - Rerun those tests after each refactoring pass. Diagnose and fix regressions before continuing.
Local simplifications and confirmed dead-code removal do not require new characterization tests. They still require relevant verification. Missing coverage calls for tests; it does not excuse a violation.
Fix Ownership
- Split oversized files into cohesive modules; extract meaningful helpers from long functions.
- Reduce nesting and branching; group related parameters only when they represent one concept.
- Fix confirmed prop drilling using existing dependency patterns. Preserve per-call configuration and concurrency behavior.
- Resolve active TODO/FIXME/HACK markers and unsafe casts. Remove stale markers only after verifying their issue is gone.
- Remove confirmed dead internal code under the shared dead-code rules. Preserve public APIs and entry points without removal authorization.
- Leave JSDoc and prose improvements to
comment-fixer; pass it any documentation findings exposed by refactoring.
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 Changed · -53 lines · -1 tokens per session 9d37d232484a
- 1mo ago Changed · +1 lines f2abaefff177
- 1mo ago Changed · -30 tokens per session e0b5000e3d8b
- 1mo ago First seen · 107 lines · 65 tokens per session scan A 32a8ba83d81d
standards-enforcer is an agent published in the GitHub repository timohaa/scopewalker-mcp (1 stars, last pushed 6d ago), licensed MIT. It adds 34 tokens to every session and 695 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
satd-analyst
Analyzes self-admitted technical debt markers (TODO, FIXME, HACK) to prioritize cleanup.
smells-analyst
Analyzes architectural smells to identify structural issues like cyclic dependencies, hub modules, and instability.
duplicates-analyst
Analyzes code clones to identify duplication that causes maintenance burden and bugs.
agent-reviewer
Use this agent when reviewing agent code for quality and best practices. Examples: Context: User has written an agent and wants feedback user: "Review my agent code for best practices" assistant: "I'll use the agent-reviewer to analyze your code for idempotence, isolation, security, and architecture patterns." User…
consistency-and-history
Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.
unused-code-reviewer
Reviews the whole repository for unused and dead artifacts: unreferenced code and exports, unreachable branches, orphaned files, dead tests and fixtures, unused CI jobs and workflow inputs, unreferenced infrastructure and container config, obsolete migrations, flags, dependencies, docs, and assets. Spawn when user…