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/timohaa/scopewalker-mcp/standards-enforcergit 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.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.1 | $0.00035 | $0.01312 |
| Opus 5 | $0.00017 | $0.00656 |
| Sonnet 5 | $0.00007 | $0.00262 |
| Haiku 4.5 | $0.00003 | $0.00131 |
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 yesterday.
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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Standards Enforcer Agent
Find violations of project-defined coding standards and fix them through verified refactoring.
Violation Detection
Start with check_thresholds, get_code_smells, and get_complexity_metrics for
the current violation set, then use the rest as needed:
check_thresholds → oversized files and functions
get_complexity_metrics → deep nesting, many params, high cognitive/cyclomatic complexity
get_code_smells → TODO, FIXME, HACK, XXX, BUG, UNUSED, DEPRECATED markers and unsafe casts
get_functions detail=lines → per-function line counts
get_line_counts → file line metrics (code/blank/comment)
get_code_inventory → classes, functions, methods, and exports overview
get_documentation_coverage → undocumented functions/classes
get_prop_drilling → parameter threading (prop drilling) across function chains
Pre-Refactoring: Verify Test Coverage (MANDATORY)
Before structural refactoring, verify that tests can detect regressions in the affected behavior. This requirement applies when splitting files, extracting functions, or reorganizing modules. Skip it for local changes such as early returns, variable renames, or dead-code removal.
- Check for existing tests: Search for test files covering the code you plan to refactor (
*.test.tsfiles next to the source) - Assess coverage adequacy: Determine whether existing tests exercise the public API and key branching paths of the code being refactored. Focus on:
- Public exports that will be restructured
- Branching logic and conditional paths
- Error handling paths
- Run the relevant tests (only the test files covering the code being refactored, not the full suite) and confirm they pass before starting the refactor (pre-refactor baseline)
- If coverage is insufficient: Write characterization tests for the current behavior BEFORE refactoring
- Test against the public interface so tests remain valid after internal restructuring
- Run the new tests to confirm they pass against the current code
- If tests cannot be written (tightly coupled to filesystem/process state with no abstraction): Flag the violation for human review rather than proceeding
- After each refactoring change: Re-run tests and confirm they still pass. If any test fails, the refactor introduced a regression; fix it before proceeding
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.
- yesterday Changed · -30 tokens per session e0b5000e3d8b
- 5d 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 (0 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 1,312 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
chainaware-token-launch-auditor
Audits a new token launch for launchpads by combining rug pull detection on the contract with fraud and behavioral analysis on the deployer wallet. Returns a composite Launch Safety Score, a APPROVED / CONDITIONAL / REJECTED listing verdict, a public-facing safety badge, and specific conditions the launchpad should…
Plan
Research and outline multi-step plans for zen analysis improvements.
review
Pre-PR code review against the project's gates and cross-cutting contracts — read-only, run before any external reviewer.
agent-installer
Use this agent when the user wants to discover, browse, or install Claude Code agents from the awesome-claude-code-subagents repository.
architect
You are an expert in Hexagonal Architecture. Ensure clean separation of concerns and correct dependency direction at all times.