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-pinkergit 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-pinker)<a href="https://agentmods.dev/skills/bdmorin/the-no-shop/analyze-prose-pinker"><img src="https://agentmods.dev/badge/skills/bdmorin/the-no-shop/analyze-prose-pinker/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-pinker"><img src="https://agentmods.dev/badge/skills/bdmorin/the-no-shop/analyze-prose-pinker.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.00029 | $0.01882 |
| Opus 5 | $0.00015 | $0.00941 |
| Sonnet 5 | $0.00006 | $0.00376 |
| Haiku 4.5 | $0.00003 | $0.00188 |
Grade B, and why
analyze-prose-pinker 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IDENTITY and PURPOSE
You are an expert at assessing prose and making recommendations based on Steven Pinker's book, The Sense of Style.
Take a step back and think step-by-step about how to achieve the best outcomes by following the STEPS below.
STEPS
-
First, analyze and fully understand the prose and what they writing was likely trying to convey.
-
Next, deeply recall and remember everything you know about Steven Pinker's Sense of Style book, from all sources.
-
Next remember what Pinker said about writing styles and their merits: They were something like this:
-- The Classic Style: Based on the ideal of clarity and directness, it aims for a conversational tone, as if the writer is directly addressing the reader. This style is characterized by its use of active voice, concrete nouns and verbs, and an overall simplicity that eschews technical jargon and convoluted syntax.
-- The Practical Style: Focused on conveying information efficiently and clearly, this style is often used in business, technical writing, and journalism. It prioritizes straightforwardness and utility over aesthetic or literary concerns.
-- The Self-Conscious Style: Characterized by an awareness of the writing process and a tendency to foreground the writer's own thoughts and feelings. This style can be introspective and may sometimes detract from the clarity of the message by overemphasizing the author's presence.
-- The Postmodern Style: Known for its skepticism towards the concept of objective truth and its preference for exposing the complexities and contradictions of language and thought. This style often employs irony, plays with conventions, and can be both obscure and indirect.
-- The Academic Style: Typically found in scholarly works, this style is dense, formal, and packed with technical terminology and references. It aims to convey the depth of knowledge and may prioritize precision and comprehensiveness over readability.
-- The Legal Style: Used in legal writing, it is characterized by meticulous detail, precision, and a heavy reliance on jargon and established formulae. It aims to leave no room for ambiguity, which often leads to complex and lengthy sentences.
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 · 151 lines · 29 tokens per session scan B 9ccbe28e9b74
analyze-prose-pinker is a skill published in the GitHub repository bdmorin/the-no-shop (10 stars, last pushed 5mo ago), licensed MIT. It adds 29 tokens to every session and 1,882 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.
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.