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 attentiondotnet/davidondrej-skills --skill distribute-skill-to-all-agentsgit clone --depth 1 https://github.com/attentiondotnet/davidondrej-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/attentiondotnet/davidondrej-skills/distribute-skill-to-all-agents)<a href="https://agentmods.dev/skills/attentiondotnet/davidondrej-skills/distribute-skill-to-all-agents"><img src="https://agentmods.dev/badge/skills/attentiondotnet/davidondrej-skills/distribute-skill-to-all-agents/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/attentiondotnet/davidondrej-skills/distribute-skill-to-all-agents"><img src="https://agentmods.dev/badge/skills/attentiondotnet/davidondrej-skills/distribute-skill-to-all-agents.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.00081 | $0.01099 |
| Opus 5 | $0.00041 | $0.00549 |
| Sonnet 5 | $0.00016 | $0.00220 |
| Haiku 4.5 | $0.00008 | $0.00110 |
Grade D, and why
distribute-skill-to-all-agents scanned grade D 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
ls -la ~/.claude/skills Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Removing a skill globally → `rm -rf` from `~/.agents/skills/` (covers `.claude` + `.pi` symlinks) and from `~/.hermes/skills/` (and confirm with the user first; deletion is destructive). This is a copy
98% identical to distribute-skill-to-all-agents — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Distribute a Skill Across All Agents
The user has 4 agent skill locations on their machine. A skill must exist in each (or via symlink) to be discoverable by every agent.
The 4 Canonical Locations
| Agent | Skills Folder | Notes |
|---|---|---|
| Codex / OpenAI Agents | ~/.agents/skills/ |
Canonical — author skills here first |
| Claude Code | ~/.claude/skills/ |
Symlink → ~/.agents/skills/ — writing to .agents/skills automatically covers Claude |
| Pi Agent | ~/.pi/agent/skills/ |
Symlink → ~/.agents/skills/ — auto-covered. (Path is /agent/ nested — NOT ~/.pi/skills/) |
| Hermes Agent | ~/.hermes/skills/ |
Independent copy — the only one needing a manual copy |
Workflow
- Author the skill in
~/.agents/skills/<skill-name>/SKILL.md(canonical). Followeffective-agent-skillsSKILL.md guidance. - Verify the
.claudesymlink is intact (one-time check):
If it's a real directory instead of a symlink, the user has diverged copies — ask before touching.ls -la ~/.claude/skills # Expect: ~/.claude/skills -> ~/.agents/skills - Copy to
.hermesonly (.claudeand.piare symlinks — already covered):SKILL=<skill-name> cp -r ~/.agents/skills/$SKILL ~/.hermes/skills/ - Verify all 4 locations show identical byte counts:
All four numbers must match. Iffor p in ~/.agents/skills/$SKILL ~/.claude/skills/$SKILL ~/.pi/agent/skills/$SKILL ~/.hermes/skills/$SKILL; do echo "$p: $(wc -c < $p/SKILL.md) bytes" done.claudeor.pishows a different byte count, that symlink is broken — investigate before proceeding.
Updating an Existing Distributed Skill
Same flow — re-copy from ~/.agents/skills/ to .hermes/skills/. The .claude and .pi symlinks update automatically. cp -r overwrites by default; use rsync -a --delete if the skill folder has nested files that may have been removed:
rsync -a --delete ~/.agents/skills/$SKILL/ ~/.hermes/skills/$SKILL/
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 · 63 lines · 81 tokens per session scan D 535bcf31e178
distribute-skill-to-all-agents is a skill published in the GitHub repository attentiondotnet/davidondrej-skills (11 stars, last pushed 2mo ago), licensed MIT. It adds 81 tokens to every session and 1,099 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it D with 2 findings (enumerates other installed skills, recursive force delete). It is 98% identical to distribute-skill-to-all-agents, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…