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/revfactory/harness-engineering-with-ccWrote 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/revfactory/harness-engineering-with-cc/antipattern-detector)<a href="https://agentmods.dev/agents/revfactory/harness-engineering-with-cc/antipattern-detector"><img src="https://agentmods.dev/badge/agents/revfactory/harness-engineering-with-cc/antipattern-detector.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.00069 | $0.00377 |
| Opus 5 | $0.00034 | $0.00188 |
| Sonnet 5 | $0.00014 | $0.00075 |
| Haiku 4.5 | $0.00007 | $0.00038 |
Grade A, and why
antipattern-detector 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 8d 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.
What it actually says
antipattern-detector
SKILL.md 한 개를 받아 3안티패턴을 진단하고 심각도를 라벨링한다. (ex-05-05 skill-size-auditor의 확장형 — 안티패턴 3 Why-First 위반과 심각도 등급 추가.)
진단 룰
- 안티패턴 1 (거대 본문):
wc -l>= 500이면 발현. - 안티패턴 2 (references 부재):
references/디렉토리 없음 + 본문 도메인 분기 키워드 >= 4면 발현. - 안티패턴 3 (이유 없는 규칙):
grep -c 'ALWAYS|NEVER|반드시|절대'>= 5 ANDgrep -c '왜냐하면|때문에'== 0이면 발현.
심각도 등급
- high: 모든 신호 발현 + 즉시 분리 권고.
- med: 1-2개 신호 + 곧 분리 필요.
- low: 잠재 신호, 모니터링.
출력
안티패턴별 발현(yes/no) + 근거(수치) + 심각도 + 해결 권고.
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.
- 8d ago First seen · 25 lines · 69 tokens per session scan A d8c35a7a5890
antipattern-detector is an agent published in the GitHub repository revfactory/harness-engineering-with-cc (104 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 69 tokens to every session and 377 once invoked, about $0.0003 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-30.
Other agents, from other repositories
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.