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 Oriolshhh/runware-image-mcp --skill threat-modelinggit clone --depth 1 https://github.com/Oriolshhh/runware-image-mcpWrote 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/oriolshhh/runware-image-mcp/threat-modeling)<a href="https://agentmods.dev/skills/oriolshhh/runware-image-mcp/threat-modeling"><img src="https://agentmods.dev/badge/skills/oriolshhh/runware-image-mcp/threat-modeling/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/oriolshhh/runware-image-mcp/threat-modeling"><img src="https://agentmods.dev/badge/skills/oriolshhh/runware-image-mcp/threat-modeling.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.00018 | $0.00496 |
| Opus 5 | $0.00009 | $0.00248 |
| Sonnet 5 | $0.00004 | $0.00099 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
threat-modeling 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 8d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Threat Modeling
Purpose
Reason systematically about how a change could be abused, so security findings are concrete and prioritized rather than generic.
When to use it
- For changes touching untrusted input, auth, secrets, filesystem/command execution, dependencies, generated-file ownership, or untrusted instructions.
- During the
/councilsecurity review.
Instructions
- List the assets worth protecting (data, credentials, integrity of generated files, execution surface).
- List the actors (users, other services, malicious input, compromised deps) and the entry points they reach.
- Draw the trust boundaries the change crosses; note where untrusted data becomes trusted.
- Enumerate misuse cases: injection, traversal/symlink escape, privilege misuse, secret exposure, supply-chain tampering, prompt injection.
- For each realistic threat, give the exploit path, severity, and a concrete mitigation. Separate vulnerabilities (exploitable now) from optional hardening.
- Decide whether a fuller, standalone threat model is warranted.
Output format
A threat model: assets, actors, entry points, trust boundaries, ranked threats (each with exploit path, severity, mitigation), vulnerabilities vs. hardening, and residual risk.
Anti-patterns
- Generic checklists with no exploit path or repository evidence.
- Labelling optional hardening as a live vulnerability (or vice versa).
- Naming secret values instead of the configuration key or source.
- Stopping at "validate input" without identifying the specific sink.
Verification checklist
- Trust boundaries and entry points are explicit.
- Each threat has an exploit path, severity, and concrete mitigation.
- Vulnerabilities and hardening are clearly separated.
- The need for a formal threat model is decided, with reasons.
Apply
context-discoverybefore broad scanning: use a supplied context capsule first; otherwise check context frontmatter freshness, read.agent/context/routing.md, load only relevant summaries, and verify critical claims against 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.
- 8d ago First seen · 51 lines · 18 tokens per session scan A dde6cc4fab39
threat-modeling is a skill published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 496 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…