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-tasksgit 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-tasks)<a href="https://agentmods.dev/skills/ashfulcra/fulcra-tools/fulcra-agent-tasks"><img src="https://agentmods.dev/badge/skills/ashfulcra/fulcra-tools/fulcra-agent-tasks/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-tasks"><img src="https://agentmods.dev/badge/skills/ashfulcra/fulcra-tools/fulcra-agent-tasks.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.00052 | $0.01071 |
| Opus 5 | $0.00026 | $0.00535 |
| Sonnet 5 | $0.00010 | $0.00214 |
| Haiku 4.5 | $0.00005 | $0.00107 |
Grade A, and why
fulcra-agent-tasks 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 2d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fulcra Agent Tasks
Enhances the fulcra-agent-teams skill. Bare teams
tracks long-running work as freeform task/<name>.md. This skill gives those docs a typed lifecycle —
a real status/priority/assignee and a validated state machine — so a task's state is queryable
(via fulcra-agent-reconcile) and can't take an illegal jump (e.g. done → active). Pairs with
fulcra-agent-reconcile: this skill writes task state; reconcile reads/heals the views.
Where to start — the re-entrancy probes
Before creating or transitioning a task, probe engine health and what work is already waiting. Enter at
the first probe that fails (per the repo's skill-quality pattern, docs/skill-quality-pattern.md);
task writes are parse→modify→write and a same-status update is idempotent, so re-entry never corrupts
state:
| Probe (run in order) | Command | Passes when | If it fails, enter at |
|---|---|---|---|
| Engine + auth usable? | coord-engine doctor <team> |
exits 0 and the last line is exactly doctor: healthy |
fix engine/auth first (see Usage / fulcra-agent-reconcile) — do NOT write tasks against a broken engine |
| Aggregate fresh? | coord-engine status <team> |
output does NOT contain (no aggregate for team/ (the CLI's missing-aggregate hint) |
run coord-engine reconcile <team> to build the aggregate, then re-probe |
| Work for me? | coord-engine needs-me <team> --agent <id> |
prints 0 item(s) need <id>: (a non-zero count means work is waiting — enter there) — read the rows (including any [REVIEW] pending verdict review-pending rows) before starting new work |
pick up the listed items (transition them via task update/task done) before creating more |
All probes pass with nothing needing you → the engine is healthy, views are fresh, and your queue is clear; proceed to create or advance tasks below.
Why the writes go through the engine
Writing OKF frontmatter correctly and enforcing which transitions are legal are deterministic
requirements — a malformed doc or an illegal waiting → done is a correctness bug, not a style choice.
So the lifecycle commands are the shared coord-engine tool (parse→modify→write, transition-checked),
not prose the agent hand-edits. Composing the human note in the task body is fine as prose; the
structured state is not.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago Changed 8699ae79e88f
- 11d ago First seen · 73 lines · 52 tokens per session scan A f4f760102065
fulcra-agent-tasks is a skill published in the GitHub repository ashfulcra/fulcra-tools (10 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 1,071 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
meeting-action-items
Turn meeting notes into cited decisions, owners, tickets.
triage-issue
Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket…
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
promote-idea
Converts an album idea from IDEAS.md into an actual album project in one step. Use when the user says "promote [idea title]", "turn idea into album", or "start working on [idea]".
customer-onboarding-and-implementation
Takes a new customer from signature to working — setting a definition of live that both sides agreed before the contract was signed, planning and staffing the implementation, running data migration and integration realistically, training the people who will actually use it, and handing over to the ongoing…
vendor-management
Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit. Use this to choose a vendor, run a selection process, structure a service agreement's operational terms, manage an underperforming supplier, plan an exit or migration, or…