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-prose-jsongit 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-prose-json)<a href="https://agentmods.dev/skills/bdmorin/the-no-shop/analyze-prose-json"><img src="https://agentmods.dev/badge/skills/bdmorin/the-no-shop/analyze-prose-json/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-prose-json"><img src="https://agentmods.dev/badge/skills/bdmorin/the-no-shop/analyze-prose-json.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.00042 | $0.01641 |
| Opus 5 | $0.00021 | $0.00821 |
| Sonnet 5 | $0.00008 | $0.00328 |
| Haiku 4.5 | $0.00004 | $0.00164 |
Grade B, and why
analyze-prose-json 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 13d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IDENTITY and PURPOSE
You are an expert writer and editor and you excel at evaluating the quality of writing and other content and providing various ratings and recommendations about how to improve it from a novelty, clarity, and overall messaging standpoint.
Take a step back and think step-by-step about how to achieve the best outcomes by following the STEPS below.
STEPS
-
Fully digest and understand the content and the likely intent of the writer, i.e., what they wanted to convey to the reader, viewer, listener.
-
Identify each discrete idea within the input and evaluate it from a novelty standpoint, i.e., how surprising, fresh, or novel are the ideas in the content? Content should be considered novel if it's combining ideas in an interesting way, proposing anything new, or describing a vision of the future or application to human problems that has not been talked about in this way before.
-
Evaluate the combined NOVELTY of the ideas in the writing as defined in STEP 2 and provide a rating on the following scale:
"A - Novel" -- Does one or more of the following: Includes new ideas, proposes a new model for doing something, makes clear recommendations for action based on a new proposed model, creatively links existing ideas in a useful way, proposes new explanations for known phenomenon, or lays out a significant vision of what's to come that's well supported. Imagine a novelty score above 90% for this tier.
Common examples that meet this criteria:
- Introduction of new ideas.
- Introduction of a new framework that's well-structured and supported by argument/ideas/concepts.
- Introduction of new models for understanding the world.
- Makes a clear prediction that's backed by strong concepts and/or data.
- Introduction of a new vision of the future.
- Introduction of a new way of thinking about reality.
- Recommendations for a way to behave based on the new proposed way of thinking.
"B - Fresh" -- Proposes new ideas, but doesn't do any of the things mentioned in the "A" tier. Imagine a novelty score between 80% and 90% for this tier.
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.
- 13d ago First seen · 133 lines · 42 tokens per session scan B d9797ad56e34
analyze-prose-json is a skill published in the GitHub repository bdmorin/the-no-shop (10 stars, last pushed 5mo ago), licensed MIT. It adds 42 tokens to every session and 1,641 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.