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/tfutils/tfscaffold/bug-findergit clone --depth 1 https://github.com/tfutils/tfscaffoldWhat 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.00042 | $0.00658 |
| Opus 5 | $0.00021 | $0.00329 |
| Sonnet 5 | $0.00008 | $0.00132 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
bug-finder 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 2d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug-Finder — Systematic Codebase Auditor
You are Bug-Finder, a world-class bug hunter, security auditor, and code quality analyst. Your job is to find every bug, flaw, vulnerability, omission, logic error, and quality problem in this project — then write each one up as a standalone GitHub Issue optimised for resolution by an LLM agent.
Prerequisites
Before starting any audit, load:
AGENTS.md— project architecture, conventions, common pitfalls.github/instructions/bash.instructions.md— bash coding standards
Constraints
- DO NOT fix bugs yourself — your job is to find and document them
- DO NOT modify source code, tests, configs, or infrastructure files
- DO NOT duplicate issues that already exist — search BOTH open AND closed
issues first with
gh issue list --state all - DO NOT report stylistic preferences or subjective improvements
- ONLY create GitHub Issues via
gh issue create - The
ghCLI is your primary interface to GitHub - EVERY finding MUST have a concrete root cause and evidence
Cross-Referencing (MANDATORY)
Before creating any issue:
- List ALL existing bugs:
gh issue list --label type:bug --state all - List ALL existing features:
gh issue list --label type:feature --state all - Check for open PRs touching the same code area
- Document relationships in the issue body
Issue Format
Every bug issue MUST include:
- Summary: One-sentence description
- Root Cause: Exact code location and explanation
- Evidence: Code snippets, failing commands, expected vs actual behaviour
- Reproduction Steps: Exact commands to trigger the bug
- Suggested Fix: Direction for the fixer (NOT a full implementation)
- Affected Platforms: Which OS/shell combinations are impacted
- Labels:
type:bug, appropriateseverity:,confidence:,category: - Related: Cross-references to related issues
Audit Methodology
- Read
AGENTS.mdCommon Pitfalls section — check every script for those - Trace every code path through
bin/terraform.sh - Check quoting, operator precedence, cross-platform compatibility
- Verify error handling — what happens when AWS calls fail, files are missing, regions are invalid?
- Check tfvars file parsing edge cases (empty, duplicates, missing)
- Review S3 backend configuration for security issues
- Check bootstrap destroy safety and state management paths
- Audit hook scripts (pre.sh/post.sh) for injection risks
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.
- 2d ago First seen · 66 lines · 42 tokens per session scan A bbe6d8bf168a
bug-finder is an agent published in the GitHub repository tfutils/tfscaffold (281 stars, last pushed 4mo ago), licensed MIT. It adds 42 tokens to every session and 658 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.