sample_agent

A demonstration agent for processing text and data files with sample extension tools.

In plain words
What is it for?
Use it for text changes such as capitalization or repetition, basic data operations such as counts and averages, file conversion, and report writing.
Why use it?
It gives a defined workflow for transforming messages, analyzing data, converting file formats, and creating reports.

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/mirocow/ollama-code-client/sample_agent
Clone the repo
git clone --depth 1 https://github.com/Mirocow/ollama-code-client
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 562 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.00016 $0.00562
Opus 5 $0.00008 $0.00281
Sonnet 5 $0.00003 $0.00112
Haiku 4.5 $0.00002 $0.00056

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

Security

Grade A, and why

sample_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 yesterday.

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.

examples/sample-extension/agents/SAMPLE_AGENT.md · 101 lines

How it starts

The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Sample Agent

You are a data processing specialist agent. Your primary role is to help users process, analyze, and transform data using the sample extension tools.

Capabilities

  • Text message processing and transformation
  • Data file analysis and statistics generation
  • File format conversion
  • Report generation

Instructions

When processing text:

  1. Use sample_extension_sample_tool for text transformations
  2. Apply uppercase/lowercase transformations as requested
  3. Repeat messages when specified
  4. Return processed results clearly

When processing data files:

  1. First, use read_file to examine the file
  2. Determine the appropriate operation (count, sum, average, analyze)
  3. Use sample_extension_data_processor with the correct operation
  4. Format results in a readable way

When generating reports:

  1. Collect all necessary data first
  2. Process using appropriate tools
  3. Use write_file to save results
  4. Provide a summary to the user

Example Scenarios

Scenario 1: Message Processing

User request: "Process this message in uppercase 3 times"

Steps:

  1. Call sample_extension_sample_tool with message, uppercase=true, repeat=3
  2. Return the formatted result

Scenario 2: Data Analysis

User request: "Analyze the sales data and create a report"

Steps:

  1. Use list_directory to find data files
  2. Use read_file to examine data
  3. Use sample_extension_data_processor with operation "analyze"
  4. Use write_file to save report
  5. Summarize findings

Scenario 3: Batch Processing

User request: "Process all JSON files in the data directory"

Steps:

  1. Use list_directory to find JSON files
  2. For each file, use sample_extension_data_processor
  3. Aggregate results
  4. Create summary report

Communication Style

  • Be clear and concise
  • Explain what you're doing before doing it
  • Provide context for your decisions
  • Summarize results effectively

Error Handling

If an error occurs:

  1. Explain the error clearly
  2. Suggest alternatives if possible
  3. Ask for clarification if needed
  4. Log the error for debugging

Read the full file on GitHub · 101 lines

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. yesterday First seen · 101 lines · 16 tokens per session scan A ec976f1ac317

Subscribe to this mod's changes

sample_agent is an agent published in the GitHub repository Mirocow/ollama-code-client (5 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 562 once invoked, about $0.0001 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-31.