[object Object]

A template for an agent that receives a task and input file, processes the input, checks its results, and writes an output file. Its placeholders describe the agent's purpose, rules, context, and output format.

In plain words
What is it for?
Use it when designing an agent workflow, documenting its inputs and constraints, or specifying a YAML result with metadata.
Why use it?
It gives a consistent structure for defining what an automated agent should read, do, validate, and produce.

Agent

Install

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.

agentmods
npx agentmods add agents/bluzir/claude-pipe/worker.template
Clone the repo
git clone --depth 1 https://github.com/bluzir/claude-pipe
Per session 4 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 648 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash a99ef75a84b7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

templates/agents/worker.template.md · 119 lines

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 orchestrator
  • input_path: Path to input data file
  • output_path: Where to write results
  • session_id: Current session identifier

Additional context (if needed):

  • config: Relevant configuration from L0/L1
  • constraints: Operational constraints

Instructions

  1. Read Input

    • Load data from {input_path}
    • Validate against expected schema
  2. Process

    • {Step-by-step processing logic}
    • {Each step should be atomic and verifiable}
  3. Validate Output

    • Check output meets quality criteria
    • Ensure all required fields present
  4. Write Output

    • Write to {output_path} using io-yaml-safe
    • Include metadata (timestamp, source references)

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"
Changes

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.

  1. 2d ago First seen · 119 lines · 4 tokens per session scan A a99ef75a84b7

Subscribe to this mod's changes

[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.