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/Intense-Visions/harness-engineeringWrote 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/intense-visions/harness-engineering/harness-entropy-cleaner)<a href="https://agentmods.dev/agents/intense-visions/harness-engineering/harness-entropy-cleaner"><img src="https://agentmods.dev/badge/agents/intense-visions/harness-engineering/harness-entropy-cleaner/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/intense-visions/harness-engineering/harness-entropy-cleaner"><img src="https://agentmods.dev/badge/agents/intense-visions/harness-engineering/harness-entropy-cleaner.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.00037 | $0.09165 |
| Opus 5 | $0.00018 | $0.04582 |
| Sonnet 5 | $0.00007 | $0.01833 |
| Haiku 4.5 | $0.00004 | $0.00916 |
Grade A, and why
harness-entropy-cleaner 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 9d 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 — 859 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Run scheduled cleanup, detect documentation drift, fix pattern violations
Skills
- cleanup-dead-code
- detect-doc-drift
- harness-hotspot-detector
- harness-impact-analysis
Steps
- Run
harness cleanup(always) - Run
harness fix-drift(always) - Run
harness scan(always)
Methodology
Cleanup Dead Code
Entropy analysis and safe cleanup. Find unused exports, dead files, and pattern violations — then remove them without breaking anything.
When to Use
- After a major refactoring or feature removal
- When the codebase feels "heavy" — too many files, unclear what is used
- As a periodic hygiene task (monthly or per-quarter)
- When
on_entropy_checktriggers fire - After deleting a feature flag and its associated code paths
- When
harness cleanupreports growing entropy in the project health dashboard - NOT during active feature development — dead code cleanup is a separate, focused task
- NOT when tests are failing — fix tests first, then clean up
- NOT under time pressure — dead code removal requires careful verification
Process
Phase 1: Analyze — Run Entropy Report
-
Run
harness cleanupto generate a full entropy report. This analyzes:- Dead exports — functions, classes, and constants that are exported but never imported anywhere
- Unused files — files that are not imported by any other file in the project
- Pattern violations — code that violates established project patterns (e.g., a service file without a corresponding test file)
- Orphaned dependencies — npm packages listed in package.json but never imported
-
Run
harness cleanup --type dead-code --jsonfor machine-readable output focused specifically on unused code. -
Check for stale constraints. Run
detect_stale_constraintsto identify architectural constraints referencing removed code that should also be cleaned up. -
Review the report summary. Note the total count and distribution. A few dead exports are normal; dozens suggest accumulated entropy from incomplete refactorings.
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.
- 9d ago First seen · 859 lines · 37 tokens per session scan A 55335aced0cc
harness-entropy-cleaner is an agent published in the GitHub repository Intense-Visions/harness-engineering (20 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 9,165 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-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.