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 agentmods add skills/promovaweb/specsfy/fortify-developmentnpx skills add promovaweb/specsfy --skill fortify-developmentgit clone --depth 1 https://github.com/promovaweb/specsfyWrote 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/promovaweb/specsfy/fortify-development)<a href="https://agentmods.dev/skills/promovaweb/specsfy/fortify-development"><img src="https://agentmods.dev/badge/skills/promovaweb/specsfy/fortify-development.svg" alt="Measured on agentmods" 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.00199 | $0.01621 |
| Opus 5 | $0.00100 | $0.00811 |
| Sonnet 5 | $0.00040 | $0.00324 |
| Haiku 4.5 | $0.00020 | $0.00162 |
Grade A, and why
fortify-development 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 6d 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
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 6d ago First seen · 152 lines · 199 tokens per session scan A b2c1c7ef01ec
fortify-development is a skill published in the GitHub repository promovaweb/specsfy (75 stars, last pushed 2d ago), with no licence file. It adds 199 tokens to every session and 1,621 once invoked, about $0.0010 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
pn-php-scaffolding
Scaffolds new PHP API projects (Laravel, Slim) or routes. Use when adding a new controller/service; covers PSR standards, Composer hygiene, Laravel conventions, and idiomatic PHP 8.x patterns.
php-laravel
When to use: PHP or Laravel work — Eloquent, middleware, validation, queues, migrations, testing.
artisan-commands
Execute Laravel Artisan commands safely.
performant-php
High-performance modern PHP — PHP 8.4/8.5, OPcache+JIT, FrankenPHP workers, Composer, Symfony/Laravel, PHPStan/Psalm, Pest.
pw-module-development
Use when building, structuring, or refactoring native backend modules for ProcessWire using PHP 8.4 and strict typing.
pw-expert
Use when working with Laravel Prompts/Symfony Console command patterns, or when determining the correct, context-safe way to access ProcessWire API variables like $page, $pages, or $user.