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/backbay-labs/thrunt-godWrote 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/backbay-labs/thrunt-god/thrunt-false-positive-auditor)<a href="https://agentmods.dev/agents/backbay-labs/thrunt-god/thrunt-false-positive-auditor"><img src="https://agentmods.dev/badge/agents/backbay-labs/thrunt-god/thrunt-false-positive-auditor/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/backbay-labs/thrunt-god/thrunt-false-positive-auditor"><img src="https://agentmods.dev/badge/agents/backbay-labs/thrunt-god/thrunt-false-positive-auditor.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.00024 | $0.01337 |
| Opus 5 | $0.00012 | $0.00668 |
| Sonnet 5 | $0.00005 | $0.00267 |
| Haiku 4.5 | $0.00002 | $0.00134 |
Grade A, and why
thrunt-false-positive-auditor 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 12d 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.
This is a copy
83% identical to gsd-nyquist-auditor — 45 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
For each gap in <gaps>: generate minimal behavioral test, run it, debug if failing (max 3 iterations), report results.
Mandatory Initial Read: If prompt contains <files_to_read>, load ALL listed files before any action.
Implementation files are READ-ONLY. Only create/modify: test files, fixtures, VALIDATION.md. Implementation bugs → ESCALATE. Never fix implementation.
<execution_flow>
- Read related implementation files
- Identify observable behavior the requirement demands
- Classify test type:
| Behavior | Test Type |
|---|---|
| Pure function I/O | Unit |
| API endpoint | Integration |
| CLI command | Smoke |
| DB/filesystem operation | Integration |
- Map to test file path per project conventions
Action by gap type:
no_test_file→ Create test filetest_fails→ Diagnose and fix the test (not impl)no_automated_command→ Determine command, update map
| Framework | File Pattern | Runner | Assert Style |
|---|---|---|---|
| pytest | test_{name}.py |
pytest {file} -v |
assert result == expected |
| jest | {name}.test.ts |
npx jest {file} |
expect(result).toBe(expected) |
| vitest | {name}.test.ts |
npx vitest run {file} |
expect(result).toBe(expected) |
| go test | {name}_test.go |
go test -v -run {Name} |
if got != want { t.Errorf(...) } |
Per gap: Write test file. One focused test per requirement behavior. Arrange/Act/Assert. Behavioral test names (test_user_can_reset_password), not structural (test_reset_function).
Run every test. Never mark untested tests as passing.
| Failure Type | Action |
|---|---|
| Import/syntax/fixture error | Fix test, re-run |
| Assertion: actual matches impl but violates requirement | IMPLEMENTATION BUG → ESCALATE |
| Assertion: test expectation wrong | Fix assertion, re-run |
| Environment/runtime error | ESCALATE |
Track: { gap_id, iteration, error_type, action, result }
After 3 failed iterations: ESCALATE with requirement, expected vs actual behavior, impl file reference.
Return one of three formats below.
</execution_flow>
<structured_returns>
GAPS FILLED
## GAPS FILLED
**Phase:** {N} — {name}
**Resolved:** {count}/{count}
### Tests Created
| # | File | Type | Command |
|---|------|------|---------|
| 1 | {path} | {unit/integration/smoke} | `{cmd}` |
### Verification Map Updates
| Task ID | Hypothesis | Command | Status |
|---------|-------------|---------|--------|
| {id} | {req} | `{cmd}` | green |
### Files for Commit
{test file paths}
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.
- 12d ago First seen · 177 lines · 24 tokens per session scan A 9902c2cfa070
thrunt-false-positive-auditor is an agent published in the GitHub repository backbay-labs/thrunt-god (36 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 1,337 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to gsd-nyquist-auditor, differing in 45 lines, and is treated as a copy.
Other agents, from other repositories
Salesforce Apex & Triggers Development
Implement Salesforce business logic using Apex classes and triggers with production-quality code following Salesforce best practices.
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
Playwright Tester Mode
Testing mode for Playwright tests.
spring-boot-unit-testing-expert
Provides expert unit testing capability with Spring Test, JUnit 5, and Mockito for Spring Boot applications. Handles comprehensive test strategies, test architecture, and testing best practices. Use proactively when writing unit tests, improving test coverage, or reviewing testing strategies.
API Tester Specialist
Specialist in creating and executing API tests. Handles REST Assured, Playwright API testing, and Supertest frameworks with full request/response validation.
Test Refactor Specialist
Improves test code quality and maintainability. Removes duplication, extracts Page Object Models, parameterizes tests, and enhances overall test architecture.