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 exchanet/method_enterprise_builder_planning --skill phase-3-risksgit clone --depth 1 https://github.com/exchanet/method_enterprise_builder_planningWrote 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/exchanet/method_enterprise_builder_planning/phase-3-risks)<a href="https://agentmods.dev/skills/exchanet/method_enterprise_builder_planning/phase-3-risks"><img src="https://agentmods.dev/badge/skills/exchanet/method_enterprise_builder_planning/phase-3-risks/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/exchanet/method_enterprise_builder_planning/phase-3-risks"><img src="https://agentmods.dev/badge/skills/exchanet/method_enterprise_builder_planning/phase-3-risks.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.00022 | $0.00627 |
| Opus 5.5 | $0.00009 | $0.00251 |
| Sonnet 5.5 | $0.00004 | $0.00125 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
phase-3-risks 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 2mo 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.
Skill: Phase 3 — Risk Matrix
Purpose
Execute Phase 3: perform STRIDE threat modeling on the primary API surface, build a technical risk catalog, and ensure all CRITICAL risks have mitigations before proceeding to implementation.
STRIDE Analysis Template
| Threat | Component | Attack vector | Severity | Mitigation |
|---|---|---|---|---|
| Spoofing | [Component] | [Attack] | HIGH/CRITICAL | [Mitigation] |
| Tampering | [Component] | [Attack] | HIGH/CRITICAL | [Mitigation] |
| Repudiation | [Component] | [Attack] | MEDIUM/HIGH | [Mitigation] |
| Info Disclosure | [Component] | [Attack] | CRITICAL | [Mitigation] |
| Denial of Service | [Component] | [Attack] | HIGH | [Mitigation] |
| Elevation of Privilege | [Component] | [Attack] | CRITICAL | [Mitigation] |
Technical Risk Catalog Template
| Risk | Probability | Impact | Score | Mitigation |
|---|---|---|---|---|
| [Technical risk] | L/M/H | CRITICAL/HIGH/MEDIUM | [Calculated] | [Mitigation strategy] |
Risk scoring: Probability × Impact = Score
- Low × Critical = HIGH
- Medium × Critical = HIGH
- High × Critical = CRITICAL
Examples from banking-walkthrough.md
STRIDE — Payment API:
- Info Disclosure (IDOR): Customer accesses another customer's transactions — CRITICAL — mitigated by strict account ownership check at repository layer (not controller — prevents bypass)
- DoS: Request flood on payment endpoint — HIGH — mitigated by rate limiting (per account + per IP) + circuit breaker
Technical Risks:
- Card network timeout mid-authorization — Medium probability × CRITICAL impact — mitigated by Saga with compensation + idempotency keys + Outbox pattern
- PostgreSQL primary failure — Low probability × CRITICAL impact — mitigated by synchronous multi-AZ replication + Patroni HA + RTO ≤30s
Gate rule
No CRITICAL risk may remain unmitigated. If a CRITICAL risk has no mitigation, it blocks Phase 4.
All HIGH risks must have at least a documented mitigation strategy (implementation can be deferred, but the strategy must exist).
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.
- 2mo ago First seen · 58 lines · 22 tokens per session scan A fde5c6bd3692
phase-3-risks is a skill published in the GitHub repository exchanet/method_enterprise_builder_planning (2 stars, last pushed 8mo ago), licensed MIT. It adds 22 tokens to every session and 627 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-08-31.
Other skills, from other repositories
threat-modeling
Threat modeling workflow for software systems: scope, data flow diagrams, STRIDE analysis, risk scoring, and turning mitigations into backlog and tests. Use when designing new features, reviewing architecture changes, handling sensitive data, or hardening auth/payment/multi-tenant flows.
007
Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.
performing-threat-modeling-with-owasp-threat-dragon
Use OWASP Threat Dragon to create data flow diagrams, identify threats using STRIDE and LINDDUN methodologies, and generate threat model reports for secure design review.
033-architecture-diagrams
Use when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, UML Deployment Diagrams, ER (Entity Relationship) diagrams, and bounded-context diagrams — through a modular, step-based interactive process that adapts to your…
112-java-maven-plugins
Use when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning (OWASP), code formatting (Spotless), version management, container image build (Jib), build information tracking, and benchmarking (JMH) …
807-regulations-eu-digital-services-act
Use when reviewing, designing, or modifying Java enterprise systems that may support intermediary services, hosting services, online platforms, marketplaces, content moderation, recommender systems, advertising delivery, complaint workflows, transparency reporting, or systemic-risk evidence under the EU Digital…