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/create-issue-branchnpx skills add torrust/torrust-website --skill create-issue-branchgit clone --depth 1 https://github.com/torrust/torrust-websiteWhat 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.00025 | $0.00753 |
| Opus 5 | $0.00013 | $0.00377 |
| Sonnet 5 | $0.00005 | $0.00151 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
create-issue-branch 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 2d 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
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.
- 2d ago First seen · 116 lines · 25 tokens per session scan A 89706d85d56f
create-issue-branch is a skill published in the GitHub repository torrust/torrust-website (5 stars, last pushed 13d ago), licensed GPL-3.0. It adds 25 tokens to every session and 753 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-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.