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/torrust/torrust-website/add-blog-postnpx skills add torrust/torrust-website --skill add-blog-postgit clone --depth 1 https://github.com/torrust/torrust-websiteWrote 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/torrust/torrust-website/add-blog-post)<a href="https://agentmods.dev/skills/torrust/torrust-website/add-blog-post"><img src="https://agentmods.dev/badge/skills/torrust/torrust-website/add-blog-post.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 | $0.00034 | $0.03048 |
| Opus 5 | $0.00017 | $0.01524 |
| Sonnet 5 | $0.00007 | $0.00610 |
| Haiku 4.5 | $0.00003 | $0.00305 |
Grade C, and why
add-blog-post scanned grade C with 1 finding 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 3d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Post content goes here --> The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the 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.
- 3d ago First seen · 412 lines · 34 tokens per session scan C 030aa7e3876c
add-blog-post is a skill published in the GitHub repository torrust/torrust-website (5 stars, last pushed 14d ago), licensed GPL-3.0. It adds 34 tokens to every session and 3,048 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
tv-remote-ui
How this app stays usable from a TV remote (Android TV / Google TV). Read before adding or changing any interactive UI — a new page, dialog, control bar, list, card, or overlay — and before touching plugins/dpad.client.ts, utils/dpad.ts, or the Android manifest/activity. Triggers on "remote", "d-pad", "dpad", "Android…
firefox-extension
Comprehensive guide for developing WebExtensions (browser extensions) for Mozilla Firefox, including Manifest V2/V3 configuration, all WebExtension APIs, security practices, web-ext CLI, and AMO submission.
firefox-amo-publish
Package and publish this extension to Firefox / addons.mozilla.org (AMO). Use when building the Firefox zip, adjusting gecko manifest settings, preparing AMO listing copy, signing with web-ext, or answering Firefox vs Chrome packaging questions.
chrome-extension-mv3-workflow
Build, debug, and validate Chrome Extension Manifest V3 changes in this repository. Use when editing background service worker logic, content scripts, popup/options pages, permissions, or extension messaging.
issue-triage-and-repro
Triage bug reports and reproduce extension issues consistently in this repository. Use when analyzing user-reported failures, validating reproduction steps, collecting debug evidence, and preparing actionable fix notes.
release-packaging-checklist
Create and verify release artifacts for this extension using the existing build pipeline. Use when bumping versions, generating zip/crx files, computing checksums, and checking release consistency.