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 auto-updatergit 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/auto-updater)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/auto-updater"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/auto-updater/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/daddia/claude-for-strategy/auto-updater"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/auto-updater.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.00053 | $0.02367 |
| Opus 5 | $0.00026 | $0.01184 |
| Sonnet 5 | $0.00011 | $0.00473 |
| Haiku 4.5 | $0.00005 | $0.00237 |
Grade B, and why
auto-updater 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 7d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
[unified diff — FLAG: hooks can execute arbitrary code] How it starts
The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/strategy-builder-hub:auto-updater
When to use
Check installed community skills for updates; show diff; apply only after explicit human approval.
Preconditions
| Input | If missing |
|---|---|
| Hub engagement profile with installed list | Offer practice-setup |
| User approval for each apply | Never auto-apply |
Provisional mode
N/A — updates always require diff review.
Trust spine
Governance-tracking; fail-closed on skills-qa regression; security-surface diffs force human approval.
Workflow
Community skills improve. This skill notices when, shows you what changed, and applies updates only with your explicit approval.
Trust posture
Installed skills are code running inside your privileged strategy environment. An upstream repository can be compromised, transferred to a new owner, or simply change behavior in ways you don't want. This skill is designed so that no update is ever applied without you reading the diff and approving it. That's not a preference — it's the design.
Load context
~/.claude/plugins/config/claude-for-strategy/strategy-builder-hub/CLAUDE.md→ installed skills summary, update preferences (notify / manual).~/.claude/plugins/config/claude-for-strategy/strategy-builder-hub/install-log.yaml→ authoritativepinned_shaper skill (seeskill-installer/references/install-log-schema.md). Prefer the latestinstallorupdateentry over the CLAUDE.md table when they disagree.
Workflow
Step 1: Check each installed skill
For each skill in the installed list:
- Read
pinned_shafrom the latestinstallorupdateentry ininstall-log.yamlfor that skill - Fetch the current commit SHA from the source registry (the exact commit, not a tag or branch head — tags are mutable and can be retroactively rewritten by the publisher; only commit SHAs are immutable)
- Compare to the pinned SHA from install time
- If different: update available
Step 2: Diff and trust review
For each update, show the full diff:
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.
- 7d ago First seen · 207 lines · 53 tokens per session scan B 18373747851c
auto-updater is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 2,367 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). 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…
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…
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…
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…