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 itsbroken-ai/forge-plugin --skill threatgit clone --depth 1 https://github.com/itsbroken-ai/forge-pluginWrote 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/itsbroken-ai/forge-plugin/threat)<a href="https://agentmods.dev/skills/itsbroken-ai/forge-plugin/threat"><img src="https://agentmods.dev/badge/skills/itsbroken-ai/forge-plugin/threat/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/itsbroken-ai/forge-plugin/threat"><img src="https://agentmods.dev/badge/skills/itsbroken-ai/forge-plugin/threat.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.00098 | $0.03743 |
| Opus 5.5 | $0.00039 | $0.01497 |
| Sonnet 5.5 | $0.00020 | $0.00749 |
| Haiku 4.5 | $0.00010 | $0.00374 |
Grade A, and why
threat 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 1mo 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 — 332 lines — stays where its author put it; the contents beside it link to each section on GitHub.
forge:threat — STRIDE Threat Model
Build a threat model that thinks like an attacker planning an operation, not an auditor filling out a spreadsheet.
A threat model answers one question: "What can go wrong, and what are we doing about it?" If your threat model doesn't change how you build the system, it was a waste of time. This skill produces models that drive real engineering decisions.
How This Works
When invoked, you build a threat model in four phases:
- Scope — Define what you're modeling. Draw the boundary. Identify what's in, what's out, and why.
- Decompose — Break the system into components, data flows, trust boundaries, and entry points. Understand how the pieces talk to each other.
- Threaten — Apply STRIDE to every component and data flow that crosses a trust boundary. Think like the attacker. What would you try?
- Decide — Map threats to mitigations. Identify residual risks. Make explicit decisions about what you're accepting and why.
The Threat Modeling Mindset
This is not compliance. This is operational planning.
When you threat model, you are the attacker sitting across the table from the design. Your job is to find the paths through the system that the builders didn't think about. Every assumption is a potential entry point. Every "that would never happen" is a target.
Three principles:
- Attackers don't follow your architecture diagrams. They follow data flows, trust transitions, and error paths. Model what actually happens, not what the docs say happens.
- The most dangerous threats are the ones you assumed away. "We trust the internal network." "The admin panel isn't exposed." "Nobody would do that." These are where breaches start.
- A threat you've decided to accept is better than a threat you never identified. Residual risk is fine. Unknown risk is not. The goal is informed decisions, not zero risk.
STRIDE Categories
STRIDE is the lens. Apply it to every component and every data flow that crosses a trust boundary.
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.
- 1mo ago First seen · 332 lines · 98 tokens per session scan A 54fce974d253
threat is a skill published in the GitHub repository itsbroken-ai/forge-plugin (11 stars, last pushed 6d ago), licensed MIT. It adds 98 tokens to every session and 3,743 once invoked, about $0.0004 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-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.