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 bbartling/open-fdd --skill openfdd-mt-securitygit clone --depth 1 https://github.com/bbartling/open-fddWrote 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/bbartling/open-fdd/openfdd-mt-security)<a href="https://agentmods.dev/skills/bbartling/open-fdd/openfdd-mt-security"><img src="https://agentmods.dev/badge/skills/bbartling/open-fdd/openfdd-mt-security/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/bbartling/open-fdd/openfdd-mt-security"><img src="https://agentmods.dev/badge/skills/bbartling/open-fdd/openfdd-mt-security.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.00070 | $0.02226 |
| Opus 5.5 | $0.00028 | $0.00890 |
| Sonnet 5.5 | $0.00014 | $0.00445 |
| Haiku 4.5 | $0.00007 | $0.00223 |
Grade A, and why
openfdd-mt-security 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 13d 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
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 13d ago Changed · +32 lines 72aeb1766f70
- 18d ago Changed · +13 lines 5a468ae99fbe
- 21d ago Changed · +9 lines dfffcbbff6b4
- 26d ago Changed · +6 lines 6e4cbd9f1f70
- 29d ago Changed · +17 lines 2bc271eeefa7
- 1mo ago First seen · 61 lines · 70 tokens per session scan A 3eaf66108851
openfdd-mt-security is a skill published in the GitHub repository bbartling/open-fdd (174 stars, last pushed yesterday), with no licence file. It adds 70 tokens to every session and 2,226 once invoked, about $0.0003 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-16.
Other skills, from other repositories
pm-feature-design
JIT Design by Feature - Phase 6 skill. Just-In-Time technical design for a single feature before it enters build. Enriches the 4 live registers with guard conditions and finalized rules, generates a Mermaid.js sequence diagram, writes Acceptance Criteria, and completes Feature Card Sections 1-3. Replaces upfront…
pm-features-list
Generate the complete Features List in FDD format, organized by Domain > Feature Set (grouping label) > Feature. Runs Dependency Map, KANO Analysis, and Value vs. Complexity Matrix. Creates stub Feature Cards in /features/cards/ for each feature. After user approval, pushes features to Notion as the initial backlog.…
pm-prototype
Cross-phase prototyping engine. Takes a scoped chunk of the product (a feature, a PRD initiative, the whole product, or any slice) and gets a prototype of it built by one of two paths - compiled as a tool-ready spec for an external tool (Lovable, v0/Vercel, Base44, Figma Make), or built in-repo by a coding agent…
pm-reconcile
Rebuild playbook for an existing product onboarded to Pureinn. Reconciles the actual codebase against a folder of legacy documents (BRD, FSD, domain/entity models, business rules) that may contain logical, semantic and structural inconsistencies. Runs in two phases - first PLAN (inspect docs + code, define which areas…
pm-audit
Health check for an existing Pureinn workspace. Scans the framework's own artifacts - the 5 Live Registers (including the Open Questions Register), Feature Cards, roadmap, glossary, state.json - against the current Pureinn conventions, finds inconsistencies, drift, and errors, then fixes the mechanical ones and asks…
pm-hypotheses
Structure validation hypotheses, design low-cost experiments, track results, and produce a Go/No-Go decision. Runs in Phase 3a: Plan mode structures hypotheses and experiments, Results mode records outcomes and issues the Go/No-Go verdict (hard gate before Phase 3b). Based on a 5-stage SaaS validation framework.