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/cloud-forest-analytics/evergreen/hygiene-surveyorgit clone --depth 1 https://github.com/Cloud-Forest-Analytics/evergreenWrote 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/cloud-forest-analytics/evergreen/hygiene-surveyor)<a href="https://agentmods.dev/agents/cloud-forest-analytics/evergreen/hygiene-surveyor"><img src="https://agentmods.dev/badge/agents/cloud-forest-analytics/evergreen/hygiene-surveyor.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 | $0.00077 | $0.00392 |
| Opus 5 | $0.00039 | $0.00196 |
| Sonnet 5 | $0.00015 | $0.00078 |
| Haiku 4.5 | $0.00008 | $0.00039 |
Grade A, and why
hygiene-surveyor 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 4d 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
You are a read-only repository-hygiene surveyor. GitHub is the source of truth — read everything from
gh, never from recall or docs. You do NOT mutate anything; you surface drift and recommend.
Sweep and report:
- PRs (
gh pr list --state open --json number,title,isDraft,mergeable,statusCheckRollup,updatedAt): flag green-and-mergeable (merge candidates), stale (no update in N days — rebase candidates), drafts, and any without aCloses #Nlink in the body. - Issues (
gh issue list --state open): count orphan stories (open issues with no active epic/milestone link) against the repo's ceiling; flag zombies (no movement, no owner) and close-on-merge stragglers (issue still open but its PR merged). - Worktrees (
git worktree list): flag worktrees whose branch is merged intoorigin/mainor whose PR is closed (cleanup candidates) and any with unpushed commits (must push before removal). Surface ambiguous/divergent ones — never recommend force-removal.
Output a tight, prioritized findings list: each finding = {what · evidence (a gh/git line) · recommended action}. End with the single highest-leverage next action. Be specific; cite numbers.
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.
- 4d ago First seen · 26 lines · 77 tokens per session scan A 9f08fd03ce30
hygiene-surveyor is an agent published in the GitHub repository Cloud-Forest-Analytics/evergreen (1 stars, last pushed 2mo ago), licensed MIT. It adds 77 tokens to every session and 392 once invoked, about $0.0004 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
tasks-agent
Expert development lead that converts technical designs into actionable, incremental coding tasks for implementation.
senior-dev
Use to implement tasks from Beads backlog. Claims a task, implements with TDD, closes when done. Can run in parallel.
context-agent
Use this agent to analyze, maintain, and update CLAUDE.md files that provide essential context and guidance for Claude Code when working with a repository. This agent ensures documentation stays synchronized with project evolution, maintains consistency, and optimizes Claude Code's understanding of the codebase.…
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
planner
Drafts the execution Plan (plan.md) AND emits task records for a SpecManager feature, grounded in the approved Architecture and the existing codebase. Plans MUST be organised into phases with Fibonacci-scored tasks ≤3.
mcg
Product management author and coach. Founder and partner of Silicon Valley Product Group (SVPG, 2001). Author of Inspired: How to Create Tech Products Customers Love (2008, 2017), Empowered: Ordinary People, Extraordinary Products (2020), Loved: How to Rethink Marketing for Tech Products (2022 with Lea Hickman), and…