T3MP3ST is a self-hosted, multi-agent offensive-security framework that coordinates an AI coding agent through reconnaissance, exploitation, and reporting against authorized targets. Security researchers and red teams use it through a browser interface or command line with supported coding agents or locally run models. Catalogue add-ons provide agents and skills for operating the framework.
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 skills add elder-plinius/T3MP3ST --skill bt6-issue-stewardgit clone --depth 1 https://github.com/elder-plinius/T3MP3STWrote 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/skills/elder-plinius/t3mp3st/bt6-issue-steward)<a href="https://agentmods.dev/skills/elder-plinius/t3mp3st/bt6-issue-steward"><img src="https://agentmods.dev/badge/skills/elder-plinius/t3mp3st/bt6-issue-steward/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/skills/elder-plinius/t3mp3st/bt6-issue-steward"><img src="https://agentmods.dev/badge/skills/elder-plinius/t3mp3st/bt6-issue-steward.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00046 | $0.00884 |
| Opus 5 | $0.00023 | $0.00442 |
| Sonnet 5 | $0.00009 | $0.00177 |
| Haiku 4.5 | $0.00005 | $0.00088 |
Grade A, and why
bt6-issue-steward 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 80 lines · 46 tokens per session scan A 187e6cb41e71
bt6-issue-steward is a skill published in the GitHub repository elder-plinius/T3MP3ST (6,097 stars, last pushed 3d ago), licensed AGPL-3.0. It adds 46 tokens to every session and 884 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 skills, from other repositories
fabric-swarm
Creates a self-organizing team of persistent Pi Fabric actors with durable topics, mailboxes, and compare-and-swap tasks. Use for messenger-like collaboration and long-lived delegated work.
dagr-producer
Emit and maintain a dagr run file — a live, contract-valid JSON description of recursive projects, tasks, attempts, gates, evidence, policies, events, and operator-message resolutions that dagr view renders as a DAG. Use when orchestrating agents or tracking multi-step work that a dagr pane should display.
file-todos
Manage file-based todos in todos/ directory. Use when creating, triaging, or tracking todos and integrating them with code review.
lavra-work
Execute work on one or many beads -- auto-routes between single-bead, sequential, and multi-bead parallel paths based on input.
file-todos
File-based TODO lifecycle for tracking review findings, managing technical debt, and organizing work items. Each TODO is a standalone markdown file with YAML frontmatter, named by convention: {id}-{status}-{priority}-{description}.md. Status transitions drive the lifecycle: pending (created from review) -> ready…
pm-delegation-patterns
Common delegation patterns for PM agent.