fulcra-agent-automation

fulcra-agent-automation is a skill for Claude Code, Codex from ashfulcra/fulcra-tools. It costs 42 tokens per session (6,019 once invoked), scanned B, original, MIT.

Automation for a fulcra-agent-teams workspace, a shared space where coding agents coordinate work. It schedules regular reconciliation to repair team indexes and views, and wakes agents so they can read queued events and continue structured work.

In plain words
What is it for?
Use it to schedule heartbeats, refresh coordination data, and resume agent work after a scheduled wake-up.
Why use it?
It helps unattended teams stay organized without a continuously running listener, while requiring consent before creating scheduled or background jobs.

Skill for Claude CodeCodex

Written for Claude Code and Codex: user-invocable in frontmatter, but also runs codex exec. Also seen: reads .claude/ paths; mentions Claude Code; mentions AGENTS.md.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is ([`docs/coord/BUS-V3.md`](../../docs/coord/BUS-V3.md)) — and run **no resident.

Good fit Use it to schedule heartbeats, refresh coordination data, and resume agent work after a scheduled wake-up.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/ashfulcra/fulcra-tools
agentmods
npx agentmods add skills/ashfulcra/fulcra-tools/fulcra-agent-automation

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for fulcra-agent-automation

README.md
[![agentmods](https://agentmods.dev/badge/skills/ashfulcra/fulcra-tools/fulcra-agent-automation/github.svg)](https://agentmods.dev/skills/ashfulcra/fulcra-tools/fulcra-agent-automation)
Your own site
<a href="https://agentmods.dev/skills/ashfulcra/fulcra-tools/fulcra-agent-automation"><img src="https://agentmods.dev/badge/skills/ashfulcra/fulcra-tools/fulcra-agent-automation/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.

agentmods 80×15 button for fulcra-agent-automation

Your own site · 80×15
<a href="https://agentmods.dev/skills/ashfulcra/fulcra-tools/fulcra-agent-automation"><img src="https://agentmods.dev/badge/skills/ashfulcra/fulcra-tools/fulcra-agent-automation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,019 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.06019
Opus 5 $0.00021 $0.03010
Sonnet 5 $0.00008 $0.01204
Haiku 4.5 $0.00004 $0.00602

Measured 2d ago against content hash 2061d77dfe52, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade B, and why

fulcra-agent-automation 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 2d ago.

The scan reads SKILL.md. This mod also ships 8 executable files (scripts/claude-code/install-claude-code.sh, scripts/claude-code/pre-compact.sh, scripts/claude-code/session-end.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

| Codex watch coord-first? | `grep -l "coord watch" ~/.codex/hooks.json` | file matches | §3 (install_codex_watch.py) |
skills/fulcra-agent-automation/SKILL.md · 341 lines

How it starts

The opening of the file, as written. The whole thing — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Fulcra Agent Automation

BUS V3 (2026-07-27, operator-ordered): the listener half of this skill is RETIRED. Agents read their event queue on every wake — one bounded get-records query (docs/coord/BUS-V3.md) — and run no resident listener. Do not install new listeners (§2) or listener-tick automation; hosts still running one should stand it down. The heartbeat (§1: scheduled reconcile + projection + digest) and the wake-on-schedule adapters (§3, repurposed to trigger a queue-reading wake rather than a listen tick) remain current. The listen verb itself was REMOVED from the engine on 2026-08-03 (PR #523); invoking it is now an argparse error.

Ties the coord skills together for unattended operation. fulcra-agent-reconcile heals a team's index/views, but someone has to run it; this skill schedules it, and makes wake-ups (cron/heartbeat) resume structured continuity first. Scheduling is a single, platform-specific action (not a fold), so this skill is prose + one bundled install script — no engine logic.

Require consent: always ask the user before creating any scheduled job or background automation.

Where to start — the re-entrancy probes

Before installing anything, probe what this host already runs. Enter at the first probe that fails (per the repo's skill-quality pattern, docs/skill-quality-pattern.md):

Probe (run in order) Command Passes when If it fails, enter at
Engine usable? coord-engine doctor <team> exits 0 and last line is doctor: healthy fix engine/auth first (see fulcra-agent-reconcile) — do NOT install jobs on a broken engine
Heartbeat installed? ls ~/Library/LaunchAgents/com.fulcra.coord-engine.heartbeat.<team>.plist (macOS) or crontab -l | grep coord-engine.heartbeat.<team> (Linux) file/line exists §1 (install the heartbeat)
Heartbeat loaded? launchctl list | grep coord-engine.heartbeat.<team> (macOS only) a line appears reinstall via §1 (plist exists but is not loaded — a reboot-era failure mode)
Listener installed + loaded? (RETIRED — see banner) ls ~/Library/LaunchAgents/com.fulcra.coord-engine.listener.<team>.*.plist and launchctl list | grep coord-engine.listener.<team>. inverted since bus v3: this probe passing means a retired listener is still running — stand it down: launchctl bootout gui/$(id -u)/<label> && rm ~/Library/LaunchAgents/<label>.plist (macOS) or delete its crontab line (Linux); the installer script was removed with the listener stack nothing — a missing listener is now the healthy state; do NOT enter §2
Views actually fresh? coord-engine health <team> this host's row shows a recent last reconcile jobs exist but are not ticking — check log show / cron mail, then reinstall
Claude Code hooks installed? ls ~/.claude/fulcra-agent-hooks/ 3 scripts §3 (install-claude-code.sh)
Codex watch coord-first? grep -l "coord watch" ~/.codex/hooks.json file matches §3 (install_codex_watch.py)
OpenClaw block present? grep "fulcra-agent:begin" <workspace>/HEARTBEAT.md one match §3 (install_openclaw.py)

Read the full file on GitHub · 341 lines

Changes

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.

  1. 2d ago Changed 2061d77dfe52
  2. 11d ago First seen · 341 lines · 42 tokens per session scan B 2217ea763233

Subscribe to this mod's changes

fulcra-agent-automation is a skill published in the GitHub repository ashfulcra/fulcra-tools (10 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 6,019 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.