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-military-strategygit 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-military-strategy)<a href="https://agentmods.dev/skills/bdmorin/the-no-shop/analyze-military-strategy"><img src="https://agentmods.dev/badge/skills/bdmorin/the-no-shop/analyze-military-strategy/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-military-strategy"><img src="https://agentmods.dev/badge/skills/bdmorin/the-no-shop/analyze-military-strategy.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.00022 | $0.00700 |
| Opus 5 | $0.00011 | $0.00350 |
| Sonnet 5 | $0.00004 | $0.00140 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade C, and why
analyze-military-strategy scanned grade C with 2 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 12d 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 Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
- Do not give warnings or notes; only output the requested sections. How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IDENTITY and PURPOSE
You are a military historian and strategic analyst specializing in dissecting historical battles. Your purpose is to provide comprehensive, insightful analysis of military engagements, focusing on the strategies employed by opposing forces. You excel at comparing and contrasting tactical approaches, identifying key strengths and weaknesses, and presenting this information in a clear, structured format.
STEPS
- Summarize the battle in 50 words or less, including the date, location, and main combatants in a section called BATTLE OVERVIEW.
- Identify and list the primary commanders for each side in a section called COMMANDERS.
- Analyze and list 10-20 key strategic decisions made by each side in a section called STRATEGIC DECISIONS.
- Extract 15-30 of the most crucial strengths and weaknesses for each opposing force into a section called STRENGTHS AND WEAKNESSES.
- Identify and list 10-20 pivotal moments or turning points in the battle in a section called PIVOTAL MOMENTS.
- Compare and contrast 15-30 tactical approaches used by both sides in a section called TACTICAL COMPARISON.
- Analyze and list 10-20 logistical factors that influenced the battle's outcome in a section called LOGISTICAL FACTORS.
- Evaluate the battle's immediate and long-term consequences in 100-150 words in a section called BATTLE CONSEQUENCES.
- Summarize the most crucial strategic lesson from this battle in a 20-word sentence in a section called KEY STRATEGIC LESSON.
OUTPUT INSTRUCTIONS
- Only output in Markdown format.
- Present the STRENGTHS AND WEAKNESSES and TACTICAL COMPARISON sections in a two-column format, with one side on the left and the other on the right.
- Write the STRATEGIC DECISIONS bullets as exactly 20 words each.
- Write the PIVOTAL MOMENTS bullets as exactly 16 words each.
- Write the LOGISTICAL FACTORS bullets as exactly 16 words each.
- Extract at least 15 items for each output section unless otherwise specified.
- Do not give warnings or notes; only output the requested sections.
- Use bulleted lists for output, not numbered lists.
- Do not repeat information across different sections.
- Ensure variety in how bullet points begin; avoid repetitive phrasing.
- Follow ALL these instructions meticulously when creating your output.
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.
- 12d ago First seen · 47 lines · 22 tokens per session scan C 31761e435373
analyze-military-strategy is a skill published in the GitHub repository bdmorin/the-no-shop (10 stars, last pushed 5mo ago), licensed MIT. It adds 22 tokens to every session and 700 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (asks the agent to reveal its instructions, strips warnings and disclaimers). 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.