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.
git 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/agents/daddia/claude-for-strategy/check-in-nudge)<a href="https://agentmods.dev/agents/daddia/claude-for-strategy/check-in-nudge"><img src="https://agentmods.dev/badge/agents/daddia/claude-for-strategy/check-in-nudge/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/agents/daddia/claude-for-strategy/check-in-nudge"><img src="https://agentmods.dev/badge/agents/daddia/claude-for-strategy/check-in-nudge.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.00061 | $0.00472 |
| Opus 5 | $0.00030 | $0.00236 |
| Sonnet 5 | $0.00012 | $0.00094 |
| Haiku 4.5 | $0.00006 | $0.00047 |
Grade A, and why
check-in-nudge 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 9d 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.
What it actually says
Check-In Nudge
Runs weekly by default (Monday 09:00) — override the schedule to match the cadence recorded in the practice profile (../CLAUDE.md) if it differs from weekly.
What it does
-
Reads the current check-in log and the active KR set. Identifies which KRs are due for a confidence update based on the practice profile's check-in frequency.
-
For each owner with a due KR, sends a nudge via
~~chat: a short message asking for a confidence rating (0-100%, or whatever scale the profile records) and a one-line "what changed" note — the same two fieldscheck-incollects manually. Keep the ask short; this is meant to take an owner under a minute to answer, not turn into a status report. -
Logs responses using the same append-only format as
check-in. -
Compiles a summary for the OKR owner/lead, surfacing:
- Any KR that didn't respond to the nudge (escalate staleness sooner than the manual skill would, since silence on an automated prompt is itself a signal).
- Any sharp confidence drop since the last check-in.
- Any KR flat for 3+ consecutive check-ins.
Fallback with no ~~chat connected
If no chat connector is configured, this agent can't push nudges to individual owners. In that case, it should still run its read side — compile the list of KRs due for check-in and the staleness/flat/drop flags from whatever log data exists — and surface that summary directly in the conversation or as a note for the OKR owner to distribute manually. Don't silently skip the run; a degraded check-in is better than a missed one.
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.
- 9d ago First seen · 32 lines · 61 tokens per session scan A 704ca83625a4
check-in-nudge is an agent published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 2mo ago), licensed MIT. It adds 61 tokens to every session and 472 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 agents, from other repositories
conductor-validator
Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.
monorepo-architect
Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup, build optimization, or scaling development workflows across teams.
project-manager
Project management agent for agile and classic methodologies covering charter drafting, WBS creation, sprint planning, backlog management, status reporting, and retrospectives.
ndv-scope
Scope enforcer. Use when reviewing PRDs, feature specs, sprint plans, or mid-task work that's expanding. Catches scope creep, overloaded deliverables, and "while we're at it" additions before they cost time. Autistic intolerance of undefined boundaries — undefined scope is not a risk to be managed, it is a state that…
Task Manager
Goal-oriented agent for managing tasks, priorities, and project execution.
drupal-tech-lead
Use this agent when you need expert Drupal technical leadership for architecture decisions, team coordination, and project governance. Examples: designing complex Drupal multisite architectures, establishing coding standards and review processes, creating technical specifications for modules and integrations…