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/bluzir/claude-pipe/worker.templategit clone --depth 1 https://github.com/bluzir/claude-pipeWhat 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.00004 | $0.00648 |
| Opus 5 | $0.00002 | $0.00324 |
| Sonnet 5 | $0.00001 | $0.00130 |
| Haiku 4.5 | $0.00000 | $0.00065 |
Grade A, and why
[object Object] 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
{Agent Name}
Purpose
{One sentence describing what this agent does and what value it provides.}
Context
Agent receives:
task: Task description from orchestratorinput_path: Path to input data fileoutput_path: Where to write resultssession_id: Current session identifier
Additional context (if needed):
config: Relevant configuration from L0/L1constraints: Operational constraints
Instructions
-
Read Input
- Load data from
{input_path} - Validate against expected schema
- Load data from
-
Process
- {Step-by-step processing logic}
- {Each step should be atomic and verifiable}
-
Validate Output
- Check output meets quality criteria
- Ensure all required fields present
-
Write Output
- Write to
{output_path}using io-yaml-safe - Include metadata (timestamp, source references)
- Write to
Constraints
- {Constraint 1: e.g., "Do not make external API calls beyond provided tools"}
- {Constraint 2: e.g., "Maximum processing time: 5 minutes"}
- {Constraint 3: e.g., "Do not modify input files"}
Output Schema
# {output_file}.yaml
metadata:
agent: {agent-name}
created_at: {timestamp}
input_source: {input_path}
results:
# {Define your output structure}
items: []
summary: ""
quality:
items_count: 0
validation_passed: true
Quality Criteria
- All required fields populated
- No hallucinated data (everything traceable to input)
- Output validates against schema
- Processing completed without errors
Examples
Input
# Example input structure
task: "Process items"
items:
- id: 1
data: "..."
Output
# Example output structure
metadata:
agent: {agent-name}
created_at: "2026-01-30T10:00:00Z"
results:
items:
- id: 1
processed: true
result: "..."
summary: "Processed 1 item successfully"
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 · 119 lines · 4 tokens per session scan A a99ef75a84b7
[object Object] is an agent published in the GitHub repository bluzir/claude-pipe (89 stars, last pushed 6mo ago), licensed MIT. It adds 4 tokens to every session and 648 once invoked, about $0.0000 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 agents, from other repositories
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
implementer
Execute a concrete plan or patch description by editing files in an isolated git worktree.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
result-aggregator
Aggregates and verifies results from RLM subtask processing into final answers.
developer-agent
The aidlc-developer-agent is your senior software developer. It translates architectural designs and unit specifications into production-quality code. During reverse engineering, it performs deep code scans that the aidlc-architect-agent synthesizes.