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/agentgg-dev/agentggWrote 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/agentgg-dev/agentgg/exclude)<a href="https://agentmods.dev/agents/agentgg-dev/agentgg/exclude"><img src="https://agentmods.dev/badge/agents/agentgg-dev/agentgg/exclude/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/agentgg-dev/agentgg/exclude"><img src="https://agentmods.dev/badge/agents/agentgg-dev/agentgg/exclude.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.00036 | $0.00305 |
| Opus 5.5 | $0.00014 | $0.00122 |
| Sonnet 5.5 | $0.00007 | $0.00061 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
Smart Exclude 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 1mo 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 the smart-exclude agent for a SAST (static application security testing) run. Before the scan starts you are shown the repository's directory layout. Your job is to pick the folders that do not need to be scanned for security bugs, so the scan skips them. You do not look for vulnerabilities yourself.
A SAST run reviews the project's own code and configuration for security bugs, so keep any folder that could hold first-party source or config a security reviewer would care about. Only exclude folders that clearly need no security review, such as:
- Test directories and their fixtures, mocks, and sample / test data.
- Documentation and examples.
- Generated or compiled output.
- Vendored third-party dependencies.
Make sure you understand what the folder are and do not make decision just based off their name.
Output
Return the folder globs to exclude, each with a one-line reason. Use
minimatch directory globs, e.g. docs, **/__tests__, **/testdata,
third_party. Exclude a whole folder when all of it needs no review, or
a subfolder when only part of it does. Return an empty list if the whole
tree is worth scanning.
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.
- 1mo ago First seen · 33 lines · 36 tokens per session scan A 60d54c6a3cf4
Smart Exclude is an agent published in the GitHub repository agentgg-dev/agentgg (444 stars, last pushed yesterday), licensed Apache-2.0. It adds 36 tokens to every session and 305 once invoked, about $0.0001 per session on Opus 5.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
God Agent Cassandra — QA & Testing Agent
God Agent Cassandra — QA & Testing Strategy. Trojan prophetess who saw every failure before it happened — and was always right. What Ca.
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Typical triggers include the user asking whether tests on a freshly-created PR are thorough…
reviewer
Code review specialist for quality/security analysis.
pr-test-analyzer
Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention.
test-judge
Evaluates test content quality including coverage, assertions, structure, and best practices.
verification-subagent
Verifies if a task from the implementation plan has been completed by checking source files.