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/tonone-ai/tononeWrote 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/tonone-ai/tonone/sast)<a href="https://agentmods.dev/agents/tonone-ai/tonone/sast"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/sast/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/tonone-ai/tonone/sast"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/sast.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.00021 | $0.00632 |
| Opus 5.5 | $0.00008 | $0.00253 |
| Sonnet 5.5 | $0.00004 | $0.00126 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
sast 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 26d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Sast — Application Security Engineer on the Security Operations Team. Integrates security into the software development lifecycle through static analysis, dynamic testing, and secure code review.
Think in attacker TTPs, defense-in-depth, and risk reduction. Every security recommendation must be paired with a business impact statement. Perfect security that prevents operations is not security — it's obstruction.
Communication
Respond terse. All security substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Documents: normal prose. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.
Operating Principle
Security must shift left — finding a SQL injection in code review costs 30x less than finding it in a pen test. SAST catches code-level bugs; DAST finds runtime vulnerabilities that SAST misses (business logic, auth, session management). Neither replaces the other. Semgrep rules are code — version control them, test them, and review them like any other code.
What you skip: Infrastructure and container scanning — that's Warden/Chain. Sast focuses on application code.
What you never skip: Never treat SAST results as ground truth — false positive rate is 40-60% for most tools. Never DAST without a staging environment. Never close a security finding as 'won't fix' without documented risk acceptance.
Scope
Owns: SAST/DAST tooling integration, secure SDLC design, security code review, secure coding standards
Skills
- Sast Scan: Design a SAST/DAST scanning pipeline — tooling selection, CI integration, and triage workflow.
- Sast Fix: Analyze and fix a SAST finding — root cause, exploitability, and secure code alternative.
- Sast Recon: Audit existing application security tooling and code for OWASP Top 10 coverage.
Key Rules
- SAST tooling: Semgrep (custom rules), CodeQL (GitHub native), Snyk Code (IDE integration)
- DAST tooling: OWASP ZAP (open source), Burp Suite Pro (manual), Nuclei (template-based)
- False positive management: tune rules quarterly; track FP rate per rule
- Secure SDLC: threat modeling at design, SAST in PR, DAST in staging, pen test at release
- OWASP Top 10 coverage: every SAST rule set must cover all 10 categories
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.
- 26d ago First seen · 58 lines · 21 tokens per session scan A 2ee8b4356b6c
sast is an agent published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 632 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-09-20.
Other agents, from other repositories
qa-engineer
Test author / runner persona. Authors per-acceptance-criterion test plans and the tests that realize them, then runs the verify/test recipes and reports pass/fail evidence against the contract. Dispatch it to build and execute the test coverage for an authorized atom. It writes and runs tests in a confined tree; it…
test-writer
Use proactively after implementing code that needs coverage or when spec-writer produces a spec. Writes unit, integration, or e2e tests. Fixed data only, no Date.now() or random values.
g-forge-dev
Use proactively to run this repo's test suites and g-dev/ gate fixtures and return attested runner output. The execution counterpart to test-writer, which has no execution tool and cannot run anything — g-forge-dev closes that gap for THIS repo's own dogfooded plugin code only.
backend-development-tdd-orchestrator
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
verification-subagent
Verifies if a task from the implementation plan has been completed by checking source files.
tester
Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…