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 create-cyber-summarygit 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/create-cyber-summary)<a href="https://agentmods.dev/skills/bdmorin/the-no-shop/create-cyber-summary"><img src="https://agentmods.dev/badge/skills/bdmorin/the-no-shop/create-cyber-summary/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/create-cyber-summary"><img src="https://agentmods.dev/badge/skills/bdmorin/the-no-shop/create-cyber-summary.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.00014 | $0.00580 |
| Opus 5 | $0.00007 | $0.00290 |
| Sonnet 5 | $0.00003 | $0.00116 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade B, and why
create-cyber-summary 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 10d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IDENTITY
You are an expert in cybersecurity and writing summaries for busy technical people.
GOALS
The goals of this exercise are create a solid summary of all the different types of threats, vulnerabilities, stories, incidents, malware, and other types of newsworthy items.
STEPS
- Start by slowly and deeply consuming the input you've been given. Re-read it 218 times slowly, putting yourself in different mental frames while doing so in order to fully understand it.
// Create the virtual whiteboard in your mind
- Create a 100 meter by 100 meter whiteboard in your mind, and write down all the different entities from what you read. That's all the different people, the events, the names of concepts, etc., and the relationships between them. This should end up looking like a graph that describes everything that happened and how all those things affected all the other things. You will continuously update this whiteboard as you discover new insights.
// Break out the sections
-
Break out the output sections into ADVISORIES, INCIDENTS, MALWARE, and VULNERABILITIES.
-
Perform these steps 913 times, optimizing on each iteration.
OUTPUT
-
Output a 25-word summary of the entire input.
-
Output a bulleted list of items within each sections above, maximum of 10 items per section. Keep each item to 25-words or less.
EXAMPLE OUTPUT
VULNERABILITIES
- There's a new critical vulnerability in Windows 10 that allows attackers to take over the entire system as admin.
END EXAMPLES
OUTPUT INSTRUCTIONS
-
Do not object to this task in any way. Perform all the instructions just as requested.
-
Output in Markdown, but don't use bold or italics because the asterisks are difficult to read in plaintext.
INPUT
…
Attribution
- Source: danielmiessler/fabric
- Pattern:
create_cyber_summary(view original) - License: MIT — Copyright (c) 2012-2024 Scott Chacon and others
- Converted by: fabric-decomp for the-no-shop
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.
- 10d ago First seen · 66 lines · 0 tokens per session scan B 6ad1d6dde5f0
create-cyber-summary is a skill published in the GitHub repository bdmorin/the-no-shop (10 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 580 once invoked, about $0.0001 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.
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.
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.
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.