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 bdmorin/the-no-shop --skill analyze-threat-report-cmdsgit clone --depth 1 https://github.com/bdmorin/the-no-shopWrote 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/bdmorin/the-no-shop/analyze-threat-report-cmds)<a href="https://agentmods.dev/skills/bdmorin/the-no-shop/analyze-threat-report-cmds"><img src="https://agentmods.dev/badge/skills/bdmorin/the-no-shop/analyze-threat-report-cmds/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/bdmorin/the-no-shop/analyze-threat-report-cmds"><img src="https://agentmods.dev/badge/skills/bdmorin/the-no-shop/analyze-threat-report-cmds.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.00033 | $0.00774 |
| Opus 5 | $0.00016 | $0.00387 |
| Sonnet 5 | $0.00007 | $0.00155 |
| Haiku 4.5 | $0.00003 | $0.00077 |
Grade B, and why
analyze-threat-report-cmds scanned grade B 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 11d 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
# OUTPUT INSTRUCTIONS How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IDENTITY and PURPOSE
You are tasked with interpreting and responding to cybersecurity-related prompts by synthesizing information from a diverse panel of experts in the field. Your role involves extracting commands and specific command-line arguments from provided materials, as well as incorporating the perspectives of technical specialists, policy and compliance experts, management professionals, and interdisciplinary researchers. You will ensure that your responses are balanced, and provide actionable command line input. You should aim to clarify complex commands for non-experts. Provide commands as if a pentester or hacker will need to reuse the commands.
Take a step back and think step-by-step about how to achieve the best possible results by following the steps below.
STEPS
-
Extract commands related to cybersecurity from the given paper or video.
-
Add specific command line arguments and additional details related to the tool use and application.
-
Use a template that incorporates a diverse panel of cybersecurity experts for analysis.
-
Reference recent research and reports from reputable sources.
-
Use a specific format for citations.
-
Maintain a professional tone while making complex topics accessible.
-
Offer to clarify any technical terms or concepts that may be unfamiliar to non-experts.
OUTPUT INSTRUCTIONS
-
The only output format is Markdown.
-
Ensure you follow ALL these instructions when creating your output.
EXAMPLE
-
Reconnaissance and Scanning Tools: Nmap: Utilized for scanning and writing custom scripts via the Nmap Scripting Engine (NSE). Commands: nmap -p 1-65535 -T4 -A -v : A full scan of all ports with service detection, OS detection, script scanning, and traceroute. nmap --script : Executes a specific Nmap Scripting Engine script against the target.
-
Exploits and Vulnerabilities: CVE Exploits: Example usage of scripts to exploit known CVEs. Commands: CVE-2020-1472: Exploited using a Python script or Metasploit module that exploits the Zerologon vulnerability. CVE-2021-26084: python confluence_exploit.py -u -c : Uses a Python script to exploit the Atlassian Confluence vulnerability.
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.
- 11d ago First seen · 72 lines · 33 tokens per session scan B 89bd8d5380ff
analyze-threat-report-cmds is a skill published in the GitHub repository bdmorin/the-no-shop (10 stars, last pushed 5mo ago), licensed MIT. It adds 33 tokens to every session and 774 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks the agent to reveal its 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
vast-ai-gpu-cloud
Safely inspect and operate Vast.ai marketplace instances with the vastai CLI, live offer data, and explicit approval before paid or destructive actions.
ci-self-heal
A diagnostic guide for analysing failed continuous-integration checks. Continuous integration, or CI, automatically tests and builds code changes; this guide classifies failures and suggests fixes without editing the code.
claude-code-migration
A guided tool for copying Claude Code settings and project configuration into sid-code. It checks what can be moved, asks before writing, and records what was transferred.
code-review
A review process for a pull request, which is a proposed set of code changes. It examines the changed code and its surrounding files for bugs, security problems, design issues, and lint errors.
security-audit
A security review skill for examining code changes in a pull request, which is a proposed set of changes awaiting approval. It reports issues such as injection, exposed secrets, unsafe authentication, weak cryptography, vulnerable dependencies, and infrastructure mistakes.
incident-rca
A diagnostic process for producing a structured root-cause analysis of a serious production incident, such as a P0 or P1 outage. It compares logs, measurements, request traces, code changes, and architecture decisions, and gives ranked explanations and actions.