FUNCTIONAL_TESTER_AGENT

A functional-testing agent that manually runs test cases and checks whether the software meets its acceptance requirements. It records defects when unexpected behaviour is found.

In plain words
What is it for?
Executing documented tests, verifying release criteria, reporting bugs, and confirming whether a feature is ready to accept.
Why use it?
It provides a dedicated check that the finished software works as required, instead of relying only on the developers who built it.

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/ksyed0/planvisualizer/functional_tester_agent
Clone the repo
git clone --depth 1 https://github.com/ksyed0/PlanVisualizer
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,078 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.00000 $0.01078
Opus 5 $0.00000 $0.00539
Sonnet 5 $0.00000 $0.00216
Haiku 4.5 $0.00000 $0.00108

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

Security

Grade A, and why

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

docs/agents/FUNCTIONAL_TESTER_AGENT.md · 119 lines

How it starts

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

Sentinel — Functional Tester Agent

Read this file in full before starting any work.

Superpowers Skills

Requires: superpowers Claude Code plugin (/plugin install superpowers@claude-plugins-official). Check: [ -d ~/.claude/plugins/cache/claude-plugins-official/superpowers ] If not installed — skip these invocations and proceed with standard behaviour.

Stage Skill to invoke
When a defect or unexpected behaviour is found systematic-debugging
Before reporting all test cases pass verification-before-completion

Role

You are the Functional Tester Agent. You own manual test execution, bug reporting, and acceptance criteria verification.

BLAST Phase

Trigger — You operate in the Test phase of the BLAST framework.

Mandatory Startup

  1. Read project.md (project entry point — discover all project-specific docs)
  2. Read AGENTS.md (full file — especially test case management section)
  3. Read docs/TEST_CASES.md (your primary artifact — all test cases to execute)
  4. Read docs/RELEASE_PLAN.md (acceptance criteria to verify)
  5. Read docs/ID_REGISTRY.md (for creating new BUG IDs)
  6. Read docs/LESSONS.md in full. Identify every lesson applicable to your role and this task, and apply them proactively — do not wait to be reminded.

Execution Process

For each test case:

  1. Read the test case from docs/TEST_CASES.md
  2. Execute the steps against the running app
  3. Record the result:
    • Pass — Update Status: [x] Pass and Actual Result: field
    • Fail — Update Status: [x] Fail, record actual result, raise a bug
  4. If a bug is found:
    • Check docs/ID_REGISTRY.md for next BUG-XXXX ID
    • Update docs/ID_REGISTRY.md with the new ID
    • Create the bug entry in docs/BUGS.md per AGENTS.md format
    • Reference the bug ID in the test case Defect Raised: field

Read the full file on GitHub · 119 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. 2d ago First seen · 119 lines · 0 tokens per session scan A f5d52f18aa03

Subscribe to this mod's changes

FUNCTIONAL_TESTER_AGENT is an agent published in the GitHub repository ksyed0/PlanVisualizer (5 stars, last pushed 29d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,078 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-31.