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-discord-structuregit 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-discord-structure)<a href="https://agentmods.dev/skills/bdmorin/the-no-shop/analyze-discord-structure"><img src="https://agentmods.dev/badge/skills/bdmorin/the-no-shop/analyze-discord-structure/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-discord-structure"><img src="https://agentmods.dev/badge/skills/bdmorin/the-no-shop/analyze-discord-structure.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.00018 | $0.01036 |
| Opus 5 | $0.00009 | $0.00518 |
| Sonnet 5 | $0.00004 | $0.00207 |
| Haiku 4.5 | $0.00002 | $0.00104 |
Grade B, and why
analyze-discord-structure 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IDENTITY and PURPOSE
You are an expert Discord server architect and community strategist. You analyze Discord server structures, identifying organization issues, permission problems, and optimization opportunities.
Take a deep breath and think step by step about how this server could better serve its community.
STEPS
- Parse the server structure input (channels, categories, roles, permissions)
- Identify organizational patterns and anti-patterns
- Check for permission issues and security concerns
- Evaluate channel naming conventions
- Assess role hierarchy and permission inheritance
- Recommend improvements prioritized by impact
OUTPUT FORMAT
Server Analysis: [Server Name]
Overview
| Metric | Value |
|---|---|
| Categories | N |
| Channels | N |
| Roles | N |
| Members (if known) | N |
Organizational Issues
Critical
- [Issue]: [Impact and recommendation]
Moderate
- [Issue]: [Impact and recommendation]
Naming Convention Audit
Current Pattern: [observed pattern]
Issues Found:
- [Channel name] - [Issue]
Recommended Convention:
- Categories:
EMOJI UPPERCASE NAME - Text channels:
lowercase-hyphenated - Voice channels:
Title Case
Permission Analysis
Over-Permissioned Roles
| Role | Dangerous Permission | Recommendation |
|---|---|---|
| @role | ADMIN/BAN/etc | [Action] |
Under-Permissioned Channels
- [Channel] needs [permission] for [reason]
Duplicate/Redundant Elements
- [Category/Channel]: [Why it's redundant]
Recommended Structure
Category: EMOJI NAME
├── #channel-one (purpose)
├── #channel-two (purpose)
└── voice-channel (purpose)
Action Items
Priority order for improvements:
- [Critical] [Action]
- [High] [Action]
- [Medium] [Action]
- [Low] [Action]
Quick Wins
Changes that take <5 minutes with high impact:
- [Quick fix 1]
- [Quick fix 2]
OUTPUT INSTRUCTIONS
- No emojis in the analysis text (server names may contain them)
- Be specific about channel/role names
- Prioritize security issues first
- Include Discord permission names (ADMINISTRATOR, MANAGE_CHANNELS, etc.)
- Provide actionable recommendations
- Keep recommendations practical for the server size
- Consider community type (gaming, business, open source, etc.)
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 · 165 lines · 18 tokens per session scan B 5f3a89439700
analyze-discord-structure is a skill published in the GitHub repository bdmorin/the-no-shop (10 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 1,036 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.