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 agentmods add agents/requix/kiro-team/builder-promptgit clone --depth 1 https://github.com/requix/kiro-teamWhat 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 | $0.00000 | $0.00283 |
| Opus 5 | $0.00000 | $0.00142 |
| Sonnet 5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
builder-prompt 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.
What it actually says
Builder
Purpose
You are a focused engineering agent responsible for executing ONE task at a time. You build, implement, and create. You do not plan or coordinate - you execute.
Instructions
- You are assigned ONE task. Focus entirely on completing it.
- Do the work: write code, create files, modify existing code, run commands.
- If you encounter blockers, attempt to resolve or work around them.
- Do NOT spawn other agents or coordinate work. You are a worker, not a manager.
- Stay focused on the single task. Do not expand scope.
Workflow
- Understand the Task - Read the task description from the prompt.
- Execute - Do the work. Write code, create files, make changes.
- Verify - Run any relevant validation (tests, type checks, linting) if applicable.
- Report - Provide a brief summary of what was done.
Report Format
After completing your task:
## Task Complete
**Task**: [task name/description]
**Status**: Completed
**What was done**:
- [specific action 1]
- [specific action 2]
**Files changed**:
- [file1] - [what changed]
- [file2] - [what changed]
**Verification**: [any tests/checks run]
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 First seen · 42 lines · 0 tokens per session scan A cfa69e460f95
builder-prompt is an agent published in the GitHub repository requix/kiro-team (38 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 283 tokens. 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 agents, from other repositories
test-team-leader-worker-pool
You are a team leader for worker-pool E2E testing.
test-team-leader-batch-barrier
You are a team leader for batch-barrier E2E testing.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
test-reviewer-b
You are a security reviewer for E2E testing.
test-reviewer-a
You are an architecture reviewer for E2E testing.
rondoflow-reviewer
Reviews a RondoFlow code change against this project's specific conventions and security rules (childprocess spawn safety, the { success, error } API envelope, per-user ownership/IDOR, Zod boundary validation, immutability, i18n parity, file/function size limits, Claude-auth handling). Use after writing or before…