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 agentmods add skills/daddia/claude-for-strategy/disablenpx skills add daddia/claude-for-strategy --skill disablegit 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/disable)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/disable"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/disable.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.00050 | $0.00722 |
| Opus 5 | $0.00025 | $0.00361 |
| Sonnet 5 | $0.00010 | $0.00144 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
disable 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 2d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/strategy-builder-hub:disable
When to use
Temporarily disable community skill — rename SKILL.md and hooks so discovery/triggers stop; files remain for re-enable.
What this skill does not do
- Does not touch first-party plugin skills.
- Does not delete files — use
/strategy-builder-hub:uninstallfor removal. - Does not act without explicit yes.
Preconditions
| Input | If missing |
|---|---|
| Skill name | Ask |
| Install log entry (community, installed) | Refuse if not hub-installed |
Load skill-manager reference |
Required before substantive work |
Provisional mode
N/A — confirm-before-rename always.
Trust spine
Governance-tracking; install-log.yaml audit trail; built-in plugin refusal.
Workflow
Run the disable workflow from the skill-manager reference skill against the named skill.
What disable does:
- Renames the skill's
SKILL.mdtoSKILL.md.disabledso Claude no longer discovers it as an active skill. Files, references, templates, and config stay in place. - If the skill ships hooks in
hooks/hooks.json, also rename that file tohooks.json.disabledso no automatic triggers fire while the skill is disabled. - Logs the action to
~/.claude/plugins/config/claude-for-strategy/strategy-builder-hub/install-log.yaml.
Safety rules:
- Only disable community skills installed through this hub.
- Never disable a first-party plugin's skill.
- Confirm before renaming. Show the paths, get explicit
yes.
Re-enable by running the command again with the same skill name.
Detailed workflows live in the
skill-managerreference skill — load it before doing substantive work.
Worked example
Input: disable competitor-scan — community skill in install log.
Expected output: Paths shown; user confirms yes; SKILL.md → SKILL.md.disabled; log appended.
Propose profile update
When a stable convention surfaces during this run (thresholds, naming, tone, output format, or recurring corrections), propose a profile update: show the exact diff against ~/.claude/plugins/config/claude-for-strategy/strategy-builder-hub/CLAUDE.md (org-wide facts go to org-profile.md), ask for confirmation, and write only on yes. Only /strategy-builder-hub:practice-setup auto-applies a full profile write.
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.
- 2d ago First seen · 81 lines · 50 tokens per session scan A db15f5f14fc2
disable is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 722 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…
spec
Spec-driven development in the active repository's spec/{feature}/ directory. Use when user says /spec, "write a spec", "plan a feature", "create a PRD", "spec status", "spec out this epic", or references spec/ directory. Sizes work from small to epic, where an epic is a parent spec with numbered child specs.…
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…