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 fortunto2/rust-code --skill bigheadgit clone --depth 1 https://github.com/fortunto2/rust-codeWrote 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/fortunto2/rust-code/bighead)<a href="https://agentmods.dev/skills/fortunto2/rust-code/bighead"><img src="https://agentmods.dev/badge/skills/fortunto2/rust-code/bighead/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/fortunto2/rust-code/bighead"><img src="https://agentmods.dev/badge/skills/fortunto2/rust-code/bighead.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Rogue Agent · line 3 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
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.00074 | $0.00468 |
| Opus 5.5 | $0.00030 | $0.00187 |
| Sonnet 5.5 | $0.00015 | $0.00094 |
| Haiku 4.5 | $0.00007 | $0.00047 |
Grade A, and why
bighead 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 1mo 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
BigHead — Autonomous Task Loop
Named after Nelson Bighetti from Silicon Valley. You run autonomously until the task is done. The human may be asleep.
Core Loop
Each iteration: assess → plan → execute → test → commit → continue or stop.
Use .tasks/ for tracking progress across iterations. Read Makefile for available commands.
Signals
- Task complete → include
<solo:done/>in finish summary - Needs retry → include
<solo:redo/> - Control file:
echo stop > .rust-code/loop-control
Gotchas
- Commit before you forget — if you accumulate a large diff and the next step fails, you lose everything. Commit after every meaningful change, even if incomplete.
- Pre-commit hooks will bite you —
make checkruns tests + clippy + fmt. If you skip it and commit directly, the hook will reject. Alwaysmake fmtbefore committing. - Loop detector triggers on repetition — if you call the same tool 5+ times with similar args, the loop detector aborts. Vary your approach — don't retry the same failing command.
- Don't ask the human — you are autonomous. If stuck, try a different approach, read more code, check git log. Never call
ask_user. - Test command varies by project — don't assume
cargo test. ReadMakefileorpackage.jsonfirst.make helpshows all targets.
When to Stop
Include <solo:done/> when: all tasks done + tests pass + code committed + result verified.
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.
- 1mo ago First seen · 35 lines · 74 tokens per session scan A 18a2183c6917
bighead is a skill published in the GitHub repository fortunto2/rust-code (45 stars, last pushed 1mo ago), licensed MIT. It adds 74 tokens to every session and 468 once invoked, about $0.0003 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-30.
Other skills, from other repositories
hatch3r-cli-toolbox
Category-indexed reference for 34 specialist CLI tools beyond the always-on five (ripgrep, jq, gh, fd, fzf). Use to pick the right tool for HTTP clients, ai-chat, structural-search, sed-style edits, data ops, browser automation, container ops, and more.
hatch3r-handoff-prepare
Captures mid-work session state into a canonical handoff document at .hatch3r/handoffs/active/. Use when ending a session mid-work, switching tools, or after context-health Orange/Red.
hatch3r-cleanup
Repo-state cleanup pass — inventories accumulated hatch3r working state (plan files, workspace dirs, review telemetry, findings ledgers, learnings, handoffs, board staleness), asks once with per-category counts and estimated reclaim, dispatches each owned surface to its owning skill or CLI path, and prunes only the…
hatch3r-customize
Creates and manages customization files for any hatch3r artifact type (agents, commands, rules, skills). Supports model overrides, description changes, scope overrides, enable/disable control, and project-specific markdown instructions.
maestro-overlay
Create or edit command overlays from natural language, or auto-generate them from workflow deficiency signals.
maestro-help
A help system for finding commands, browsing skills, recommending workflows, and guiding new users.