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 check-ingit 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/check-in)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/check-in"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/check-in/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/check-in"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/check-in.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.00065 | $0.01083 |
| Opus 5 | $0.00032 | $0.00541 |
| Sonnet 5 | $0.00013 | $0.00217 |
| Haiku 4.5 | $0.00006 | $0.00108 |
Grade A, and why
check-in 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 10d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check-In
When to use
Confidence pulse on KRs — "honest % chance of hitting target by cycle end" — not a project status update. Appends to persistent check-in log.
What this skill does not do
- Does not replace project status reports — route to
/pmo:status-report. - Does not score the cycle — route to
/okr:score-and-retro. - Does not set targets — route to
/okr:set-targets.
Preconditions
| Input | If missing |
|---|---|
| KRs due for check-in | Ask which KRs to pulse |
| Practice profile (frequency, scale) | Default 0–100% confidence; flag [PROVISIONAL] |
| Existing check-in log (if any) | Start new log; note first entry |
Provisional mode
Without prior log: no staleness/flat flags on first round; sharp-drop flags N/A until second entry.
Trust spine
- Confidence bands (
governance-tracking):- High: Every KR has confidence + what-changed line; flags applied per rules.
- Medium: Some KRs missing what-changed — flag incomplete entries.
- Low: Status-update narrative substituted for confidence numbers — reject format.
- Failure modes:
- Strategic advice vs. support: Surfaces confidence and flags; does not recommend abandoning KRs.
- Client confidentiality: Check-in log may be internal — CONFIDENTIAL header.
- Accountability gap: Flat confidence across 3+ check-ins forces conversation flag.
- Analytical Rigor: N/A — tracking shape.
- Incentive Gaming: Flat or inflated confidence without what-changed flagged as disengagement pattern.
- Escalation triggers: Sharp confidence drop — surface prominently for manager conversation.
Workflow
- Read practice profile for check-in frequency and scoring scale.
- Get current check-in log — append only, never restart.
- For each KR due: confidence rating + required one-line what-changed.
- Flag staleness — no check-in past one cycle beyond profile frequency.
- Flag flat confidence — unchanged across 3+ consecutive check-ins.
- Flag sharp drops — significant fall since last check-in.
- Gaming-pattern check before output: confidence numbers have what-changed rationale.
- Persist full updated log (append-only).
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.
- 10d ago First seen · 113 lines · 65 tokens per session scan A 0d2b039e63df
check-in is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 2mo ago), licensed MIT. It adds 65 tokens to every session and 1,083 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
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
task-coordination-strategies
Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.