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 azmym/agent-skills --skill usedgit clone --depth 1 https://github.com/azmym/agent-skillsWrote 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/azmym/agent-skills/used)<a href="https://agentmods.dev/skills/azmym/agent-skills/used"><img src="https://agentmods.dev/badge/skills/azmym/agent-skills/used/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/azmym/agent-skills/used"><img src="https://agentmods.dev/badge/skills/azmym/agent-skills/used.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.00067 | $0.01444 |
| Opus 5 | $0.00034 | $0.00722 |
| Sonnet 5 | $0.00013 | $0.00289 |
| Haiku 4.5 | $0.00007 | $0.00144 |
Grade A, and why
used scanned grade A with 0 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 9d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Usage Tracker
Show which skills, hooks, rules, plugins, and MCP tools were activated in the current conversation.
Arguments
- No arguments (default): report usage for the last user prompt and Claude response only
sessionor--session: report usage for the entire session (since last/clearor session start)
Parse the arguments from: $ARGUMENTS (accept both session and --session as the session flag)
Instructions
When this skill is invoked, scan the current conversation context and report what was used. Follow these detection rules exactly.
1. Detect Skills
Scan the conversation for:
<command-name>tags: extract the value (e.g.,superpowers:brainstormingfrom<command-name>/superpowers:brainstorming</command-name>or<command-name>superpowers:brainstorming</command-name>)- Skill tool invocations in the conversation flow (where Claude called the Skill tool with a skill name)
Collect all unique skill names found.
2. Detect Hooks
Scan <system-reminder> tags for these patterns:
- Text containing "hook additional context" (e.g., "SessionStart hook additional context", "UserPromptSubmit hook additional context")
- Extract the hook name from the text before "hook additional context"
Collect all unique hook names found. Normalize to lowercase-kebab-case (e.g., "SessionStart" becomes "session-start", "UserPromptSubmit" becomes "user-prompt-submit").
3. Detect Rules
Scan the conversation for <system-reminder> blocks that contain # claudeMd sections. Within those sections, look for lines matching:
Contents of .../.claude/rules/<name>.md- extract<name>as the rule name- References to project-level
CLAUDE.mdfiles - report as "CLAUDE.md (project)" or similar
Collect all unique rule names found.
4. Detect Plugins
Scan the conversation for:
<system-reminder>blocks containing "# MCP Server Instructions" followed by## <plugin-name>headings - extract the plugin name<available-deferred-tools>blocks containing tool names prefixed withmcp__<plugin>__- extract unique plugin names from the prefix- Skill names that contain a colon prefix (e.g.,
superpowers:brainstorming) - the part before the colon is the plugin name - Plugin-sourced skills listed in
<system-reminder>skill availability blocks (e.g., "- superpowers:writing-plans: ...")
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 127 lines · 67 tokens per session scan A 31c1831f6e72
used is a skill published in the GitHub repository azmym/agent-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 67 tokens to every session and 1,444 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
mcporter
List, auth, and call MCP servers/tools from the terminal.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
telegram-setup
Connect a Telegram bot to the Vellum Assistant gateway with automated webhook registration and credential storage.