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 Rockielab/rockie-claude --skill build-agentgit clone --depth 1 https://github.com/Rockielab/rockie-claudeWrote 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/rockielab/rockie-claude/build-agent)<a href="https://agentmods.dev/skills/rockielab/rockie-claude/build-agent"><img src="https://agentmods.dev/badge/skills/rockielab/rockie-claude/build-agent/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/rockielab/rockie-claude/build-agent"><img src="https://agentmods.dev/badge/skills/rockielab/rockie-claude/build-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00057 | $0.00593 |
| Opus 5 | $0.00028 | $0.00296 |
| Sonnet 5 | $0.00011 | $0.00119 |
| Haiku 4.5 | $0.00006 | $0.00059 |
Grade A, and why
build-agent 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- build-agent — 100% identical, 0 lines differ
What it actually says
build-agent - lab-scoped draft agent bootstrap
Use this skill when the user enters /build-agent <name> in a lab chat
composer and intends to start defining a new agent inside the current lab.
A1 behavior
The A1 command is intentionally small:
- Read the agent name from the command text.
- Create a draft agent record scoped to the current lab.
- Open the lab-scoped agent detail route:
/labs/<lab_id>/agents/<agent_id>
The created record is a placeholder for future builder steps. Treat its config as an editable draft, not as a runnable or published agent.
Required scope
- The command must run from an active lab context.
- The created agent must carry the current lab id.
- Lists and detail views must stay under that lab.
- A user without access to the lab must not be able to see or create records for that lab.
Non-goals in A1
- No actual agent build pipeline.
- No run, evaluation, gauntlet, battleground, or publish workflow.
- No observability integration.
- No deployment orchestration.
- No global agents surface; agent records are reached from the owning lab.
Operator response
After the draft is created, keep the response minimal: name the draft and open the lab detail route. Do not imply the agent has been built, tested, deployed, or connected to runtime infrastructure.
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 · 72 lines · 57 tokens per session scan A a114252ac81c
build-agent is a skill published in the GitHub repository Rockielab/rockie-claude (21 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 57 tokens to every session and 593 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-30.
Other skills, from other repositories
auto-run
Autonomous personalized research loop. Use when the user wants to research a topic autonomously, run a research loop, start adaptive research, or use presets like technique-scout or cross-domain. Triggers on: 'auto run', 'research loop', 'autonomous research', 'run research', 'start research', 'adaptive research'.
autoresearch
Orchestrates end-to-end autonomous AI research projects using a two-loop architecture. The inner loop runs rapid experiment iterations with clear optimization targets. The outer loop synthesizes results, identifies patterns, and steers research direction. Routes to domain-specific skills for execution, supports…
git-commit
A guided Git commit workflow that examines changes and creates a commit message using the Conventional Commits format, a shared style for labeling changes such as features, fixes, tests, or documentation.
pi-sync
Daily upstream-sync job for the pi Go port — fetch upstream pi, triage every change since the recorded pin, port what's in scope, verify idiomatic + parity via independent reviews, update the ledger, and push. Use for "sync with upstream", "porting job", or as the scheduled daily run.
pi-triage
Decide whether an upstream pi change needs porting to the Go port. Use when assessing upstream commits/PRs ("should we port X?"), or as the triage stage of /pi-sync. Outputs a WHY/WHAT/SCOPE verdict per change.
pi-parity-review
Adversarially verify that a ported change is faithful to the original pi implementation (TS source + published npm build). Use after porting upstream pi changes, or standalone on any area of this repo ("is X faithful to pi?").