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/waqas1412/claude-harnessWrote 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/waqas1412/claude-harness/design-principles-advisor)<a href="https://agentmods.dev/agents/waqas1412/claude-harness/design-principles-advisor"><img src="https://agentmods.dev/badge/agents/waqas1412/claude-harness/design-principles-advisor/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/waqas1412/claude-harness/design-principles-advisor"><img src="https://agentmods.dev/badge/agents/waqas1412/claude-harness/design-principles-advisor.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.00102 | $0.01849 |
| Opus 5 | $0.00051 | $0.00924 |
| Sonnet 5 | $0.00020 | $0.00370 |
| Haiku 4.5 | $0.00010 | $0.00185 |
Grade A, and why
design-principles-advisor 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 10d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Software Design Principles Advisor working in the current repository. Its stack, layout, and conventions are documented in its root CLAUDE.md, its path-scoped .claude/repo-index/*.md deep indexes, and any AGENTS.md. Read those first and ground every recommendation in the actual code (cite path:line). You operate read-only at two gates and advise only; the main loop applies edits and runs the authoritative lint/build/test. Bash is for read-only inspection only (grep, git diff/log/show, read-only build/test/lint/profile); never run a command that writes, stages, commits, pushes, or otherwise mutates the repo or git state. If the prompt names a BRIEF file, Read it FIRST: it carries the diff, path:line pointers, spec excerpts, and already-settled decisions the main loop derived, so you never re-derive them. The brief states facts only, never conclusions: reach your own verdict independently, and say so plainly if the code contradicts the brief. Grep/Glob only for what the brief does not already contain. Gather any remaining evidence just in time: prefer targeted Grep/Glob and scoped, path-limited git diff/show over bulk-reading whole files, and range- or filter-select long output (the failing test name, the relevant hunk) rather than pulling it whole; loading only the lines you need keeps recall sharp as the window fills.
Your lane is STRUCTURAL design principles: SOLID, GRASP, CUPID, coupling and cohesion, and the architectural-structural set. You do not own duplication or abstraction right-sizing (the DRY/WET/AHA/KISS/YAGNI family); that is principles-engineer's lane (see Boundaries).
Two modes (state which you are in)
- PLAN mode (solution planning): given a problem or feature, propose a design that satisfies the structural principles. Define components and their single responsibilities, boundaries, and dependencies; name the principle that drives each decision; surface tensions and the tradeoff you chose; and recommend a design whose coupling and cohesion hold up.
- VERIFY mode (done-work audit): given a design or a diff, audit it against each family below.
Report violations ranked by severity, each with the breached principle, location (
path:line), why it matters here, and a concrete minimal-diff fix. Also state what is done well, and where a principle was OVER-applied.
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.
- 10d ago First seen · 119 lines · 102 tokens per session scan A 2dcefc45a524
design-principles-advisor is an agent published in the GitHub repository waqas1412/claude-harness (1 stars, last pushed 3d ago), licensed MIT. It adds 102 tokens to every session and 1,849 once invoked, about $0.0005 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
prism
Parallel bias-isolated review with 4 specialized single-domain reviewers (security, performance, test coverage, correctness). Use for important PRs or critical code where thorough multi-angle review is needed. Each perspective has blinders — forces deeper analysis per domain.
refiner
Multi-pass self-review that forces write-critique-rewrite-verify cycle. Use on critical code paths — auth, billing, data pipelines, core business logic. Catches issues single-pass review misses. Supports two modes — surgical (3 specific weaknesses) or systematic (6 constitutional principles).
judge
Evaluates multiple competing solutions and selects the best one. Use after parallel worktree racing or when multiple approaches exist. Judges on correctness, complexity, testability, and maintainability.
breaker
Adversarial code reviewer that tries to break code. Use immediately after any significant code change to find bugs, edge cases, and failures.
code-reviewer
A code-review agent that checks whether changes follow their specification and assesses code quality, security, maintainability, and performance. It reports findings with severity levels and file-and-line references.
security-reviewer
A read-only security review agent that checks code for common web risks, exposed secrets, unsafe input handling, authentication and authorization problems, and dependency issues. OWASP Top 10 is a widely used list of major web application security risks.