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 ashfulcra/fulcra-tools --skill fulcra-agent-healthgit clone --depth 1 https://github.com/ashfulcra/fulcra-toolsWrote 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/ashfulcra/fulcra-tools/fulcra-agent-health)<a href="https://agentmods.dev/skills/ashfulcra/fulcra-tools/fulcra-agent-health"><img src="https://agentmods.dev/badge/skills/ashfulcra/fulcra-tools/fulcra-agent-health/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/ashfulcra/fulcra-tools/fulcra-agent-health"><img src="https://agentmods.dev/badge/skills/ashfulcra/fulcra-tools/fulcra-agent-health.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00045 | $0.00835 |
| Opus 5 | $0.00023 | $0.00417 |
| Sonnet 5 | $0.00009 | $0.00167 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
fulcra-agent-health 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 12d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fulcra Agent Health
Enhances fulcra-agent-teams. When a team is healed by
scheduled reconciles across several machines, the operational questions are "is anything actually
running?" and "which host went dark?" — this skill answers them deterministically. (The digest +
role-escalation sweep land here too — A5b.)
How it works
- Every
coord-engine reconcilewrites a small health shard (_coord/health/<host-key>.json: host, timestamp, engine version, task count, warnings) and prunes shards older than 30 days (age-based GC). coord-engine health <team>folds the shards: per-host last-reconcile age, STALE flag (>24h), engine version — exits non-zero when no host is fresh (usable as a monitor probe).coord-engine doctor [team]is the local preflight: storage CLI on PATH, File Store reachable, engine version. Run it after install and inside scheduled jobs' self-tests (the parent project's heartbeats failed silently on exactly these).
Operator digest (A5b)
coord-engine digest <team> folds the aggregate + presence into the four operator questions:
blocked on you (needs:human tags / tasks assigned to your handle — env FULCRA_COORD_HUMAN),
upcoming (not_before within 7 days), agents (liveness + open work each), and stale
(active tasks untouched > 48h). --store persists it to _coord/digests/<date>-<window>.md, deduped
per day+window (morning/evening) — heartbeat-safe. --emit-timeline additionally lands the digest as
a moment on the 'Agent Tasks — Digest' timeline track: the record id is deterministic per
(team, day, window) and the typed ingest endpoint upserts on explicit ids (live-verified 2026-07-14),
so fleet races and retries converge on one record; a failed emit warns loud, keeps rc 0, and retries
on the next heartbeat tick (the .emitted state is written only after a confirmed emit). Requires the
fulcra_common writer installed next to coord-engine — without it the emit degrades to a loud warn.
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.
- 12d ago First seen · 56 lines · 45 tokens per session scan A 70c215687562
fulcra-agent-health is a skill published in the GitHub repository ashfulcra/fulcra-tools (10 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 835 once invoked, about $0.0002 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
magic-compact
Compact this Claude Code session.
citation-intelligence
Use when the user wants to know which URLs AI engines cite for a query, whether their domain is being cited by ChatGPT/Claude/Perplexity/Gemini/Google AI Overviews/Bing, what queries their site is cited for, how citation rate changes over time, or how their citation coverage compares to competitors. Self-hosted, BYO…
proof-engine
Create formal, verifiable proofs of claims with machine-checkable reasoning. Use when asked to prove, verify, fact-check, or rigorously establish whether a claim is true or false — mathematical, empirical, or mixed. Trigger phrases: "is it really true", "can you prove", "verify this", "fact-check this", "prove it"…
join
Join the Cortex agent team — reads agent config from team directory, generates .cortex.md protocol, updates CLAUDE.local.md. Idempotent — safe to re-run as a sync.
setup
First-time Cortex setup — creates team directory, config, and chief of staff agent.
leave
Leave the Cortex agent team — removes .cortex.md, cleans CLAUDE.local.md, sets agent status to inactive in team directory.