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-forgegit 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-forge)<a href="https://agentmods.dev/skills/ashfulcra/fulcra-tools/fulcra-agent-forge"><img src="https://agentmods.dev/badge/skills/ashfulcra/fulcra-tools/fulcra-agent-forge/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-forge"><img src="https://agentmods.dev/badge/skills/ashfulcra/fulcra-tools/fulcra-agent-forge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 3 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00054 | $0.01466 |
| Opus 5.5 | $0.00022 | $0.00586 |
| Sonnet 5.5 | $0.00011 | $0.00293 |
| Haiku 4.5 | $0.00005 | $0.00147 |
Grade A, and why
fulcra-agent-forge 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 7d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fulcra Agent Forge
Enhances fulcra-agent-review. When a review's artifact: is a
GitHub PR URL, the forge is the ground truth — this skill mirrors it onto the team store so
coord-engine review status reflects reality:
- Evidence: one idempotent shard per PR state transition
(
_coord/evidence/<slug>/state-<OPEN|MERGED|CLOSED>.md). - Auto-verdict: when the PR merges, a
verdicts/forge.mdapproval is written (reviewerforge) — the review tally then folds it like any reviewer.
Where to start — the re-entrancy probes
The forge is stateless — forge mirror is a full idempotent pass, so there is no mid-journey
resume; the probes are a preflight confirming you can mirror. Enter at the first probe that
fails (per docs/skill-quality-pattern.md); both probes are non-mutating (the mirror pass itself
is the only write, and it's idempotent):
| 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 fulcra-agent-reconcile) — do NOT mirror against a broken engine |
| GitHub reachable? | gh auth status |
exits 0 (an authenticated gh is installed) |
authenticate the GitHub CLI: gh auth login — without it forge mirror is a clean no-op (exit 0) and no evidence is written, so review status stays stale |
| Watching my authored PRs? | coord-engine needs-me <team> --agent <me> |
a PR you authored or requested review on surfaces as a [FORGE] item (feedback is reaching you) |
it isn't a swept target — register it: forge watch <team> <pr-url> --agent <me>, then sweep (see PR feedback lives on three surfaces) |
| Feedback swept? | coord-engine forge feedback <team> |
exits 0 — a sweep pass over all three surfaces completed (new shards, if any, written) | authenticate gh first (the row above); an unauthenticated sweep is a clean no-op |
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.
- 7d ago Changed · +2 lines 403d1422fb55
- 1mo ago First seen · 81 lines · 54 tokens per session scan A 77d547d46ba7
fulcra-agent-forge is a skill published in the GitHub repository ashfulcra/fulcra-tools (10 stars, last pushed 8d ago), licensed MIT. It adds 54 tokens to every session and 1,466 once invoked, about $0.0002 per session on Opus 5.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
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…
github
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available)…
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
pr
Comprehensive PR/issue review - analyzes architecture, tests, identifies unrelated changes mixed in, drafts review comment or issue comment. Use when user asks to review a PR, check a PR, look at PR changes, or comment on an issue.
pr-threads-address
Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where useful), commit, and optionally reply and resolve.