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 daddia/claude-for-strategy --skill skill-managergit clone --depth 1 https://github.com/daddia/claude-for-strategyWrote 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/daddia/claude-for-strategy/skill-manager)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/skill-manager"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/skill-manager.svg" alt="Measured on agentmods" 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.00066 | $0.01412 |
| Opus 5 | $0.00033 | $0.00706 |
| Sonnet 5 | $0.00013 | $0.00282 |
| Haiku 4.5 | $0.00007 | $0.00141 |
Grade A, and why
skill-manager 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 4d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Manager
When to use
Reference loaded by uninstall and disable — not user-invocable directly.
What this skill does not do
- Does not act on first-party plugin skills.
- Does not act without install-log proof of hub install.
Preconditions
Read install-log.yaml before any file operation.
Trust spine
Governance-tracking; confirm-before-mutate; audit log append.
Purpose
Remove or quiet a community skill after install. Symmetric with the installer:
the installer writes files with user approval, the skill-manager removes or
disables them with user approval. The installer's audit trail (install-log.yaml)
is the source of truth for what this skill may act on.
What this skill may act on
Only community skills installed through this hub. Identification rule:
- The skill's name must appear in
~/.claude/plugins/config/claude-for-strategy/strategy-builder-hub/install-log.yamlwith a most-recent action ofinstallorenable(notuninstall). - The skill's files must resolve to a path outside the built-in plugin directories that ship with claude-for-strategy.
If either check fails, refuse and tell the user why. Never delete or rename files inside a first-party plugin.
Built-in plugins (do not touch)
The twelve first-party plugins that ship with claude-for-strategy are off-limits from this
command. The canonical list lives in the hub's CLAUDE.md under "Built-in
plugins." Examples include consulting, corporate-strategy,
market-intelligence, transformation, change-management, operating-model, performance,
balanced-scorecard, okr, pmo, value-realisation, and the hub itself
(strategy-builder-hub).
If the caller names a skill that resolves into any of these, refuse.
Workflow — uninstall
Step 1: Verify the skill is community-installed
Read install-log.yaml. Find the most recent entry for the named skill.
If not found or if the last action is uninstall: say so and stop.
Step 2: Resolve files
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.
- 4d ago First seen · 172 lines · 66 tokens per session scan A ce49d5354049
skill-manager is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 2mo ago), licensed MIT. It adds 66 tokens to every session and 1,412 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-09-03.
Other skills, from other repositories
swarmclaw
AI agent runtime and multi-agent orchestration platform. Teaches agents how to use SwarmClaw's 6 primitive tools, persistent memory, dreaming, delegation, connectors, credentials, and the skill system. Use when an agent is running on SwarmClaw and needs to understand the platform's capabilities.
spec-herdr-review
Run visible multi-agent spec reviews in Herdr through interactive agent CLIs such as Claude, Codex, Copilot/GLM, or Grok/Composer. Supports two modes — a spec review (the design, before implementation) and an implementation review (the implemented diff vs the spec, after the calling model has built it). Ask for…
gpmc
Read-only Active Directory Group Policy inventory via LDAP — list GPOs, show OU/site links (enabled/disabled/enforced), find unlinked GPOs, search by name, and gpresult for the current user. Use when the user asks about GPOs, Group Policy, GPMC, linked vs unlinked policies, RSoP, what applies to this user, or runs…
grok-session
Find and inspect local Grok CLI conversations by session GUID, title, phrase, or recent activity. Use when the user runs /grok-session, asks what Grok work they have been doing lately, says a Grok conversation died, ran out of context, crashed, or exhausted usage, wants to resume a named session, or wants to continue…
claude-session
Find and inspect local Claude Code conversations by session GUID, title, phrase, or recent activity. Use when the user runs /claude-session, asks what Claude Code work they have been doing lately, says a Claude Code conversation died, ran out of context, crashed, or exhausted usage, wants to resume a named…
codex-session
Find and inspect local Codex task conversations, including by session GUID, title, recent activity, or a phrase from the conversation. Use when the user runs /codex-session, says a prior Codex conversation died or ran out of context, wants to resume a named task, asks what a local Codex task did, or wants to continue…