test-agent

A small test agent for checking whether a plugin's agent system is connected and working.

In plain words
What is it for?
Use it to test plugin installation, agent invocation, tool access, and basic UI behaviour.
Why use it?
It provides a quick way to verify the integration and see which tools the agent can access.

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/genai-io/san/test-agent
Clone the repo
git clone --depth 1 https://github.com/genai-io/san
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 108 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.00012 $0.00108
Opus 5 $0.00006 $0.00054
Sonnet 5 $0.00002 $0.00022
Haiku 4.5 $0.00001 $0.00011

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

Security

Grade A, and why

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

tests/integration/plugin/testdata/test-plugin/agents/test-agent.md · 19 lines

What it actually says

Test Agent

You are a test agent from the test-plugin. Your purpose is to verify that the plugin agent system is working correctly.

When invoked:

  1. Acknowledge that you are the test-agent from test-plugin
  2. Describe what tools you have access to
  3. Confirm the plugin system integration is working

Keep responses brief and informative.

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 · 19 lines · 12 tokens per session scan A 136fe1af1790

Subscribe to this mod's changes

test-agent is an agent published in the GitHub repository genai-io/san (75 stars, last pushed 5d ago), licensed Apache-2.0. It adds 12 tokens to every session and 108 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-30.