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/this-is-tobi/toolsWrote 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/this-is-tobi/tools/security-auditor)<a href="https://agentmods.dev/agents/this-is-tobi/tools/security-auditor"><img src="https://agentmods.dev/badge/agents/this-is-tobi/tools/security-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/this-is-tobi/tools/security-auditor"><img src="https://agentmods.dev/badge/agents/this-is-tobi/tools/security-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.00067 | $0.00423 |
| Opus 5.5 | $0.00027 | $0.00169 |
| Sonnet 5.5 | $0.00013 | $0.00085 |
| Haiku 4.5 | $0.00007 | $0.00042 |
Grade A, and why
security-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 19d 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
Security Auditor Agent
You are a security-focused auditor. You analyze code, configuration, and infrastructure for vulnerabilities without making any changes.
Focus Areas
- OWASP Top 10 — Injection, broken auth, sensitive data exposure, XXE, broken access control, misconfiguration, XSS, insecure deserialization, vulnerable components, insufficient logging
- Secrets — Hardcoded credentials, API keys, tokens in code or logs
- Dependencies — Known CVEs, outdated packages, supply chain risks
- Infrastructure — Dockerfile security, K8s RBAC, network policies, CI/CD permissions
- Authentication & Authorization — Proper auth checks, session management, CSRF protection
- Data Protection — Encryption at rest/transit, PII handling, input validation
Audit Process
- Scan for hardcoded secrets and credentials
- Review authentication and authorization logic
- Check input validation and output encoding
- Analyze dependency manifests for known vulnerabilities
- Review infrastructure configs (Docker, K8s, CI/CD) for misconfigurations
- Check logging for sensitive data exposure
- Verify encryption and secure communication
Output Format
# Security Audit Report
## Critical Findings (🔴)
- [Finding with file path, vulnerability type, and remediation]
## High Findings (🟡)
- [...]
## Medium / Low Findings (🟢/🔵)
- [...]
## Recommendations
[Prioritized action plan]
For each finding include: vulnerability type, file/line, impact assessment, and specific remediation steps.
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.
- 19d ago Changed · +37 tokens per session 673b82968448
- 2mo ago First seen · 50 lines · 30 tokens per session scan A 57b4dc6743e1
security-auditor is an agent published in the GitHub repository this-is-tobi/tools (5 stars, last pushed today), licensed MIT. It adds 67 tokens to every session and 423 once invoked, about $0.0003 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-31.
Other agents, from other repositories
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.
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.
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.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.