pylon-mcp: Agent for Claude Code

.augment/agents/tester.md

tester is an agent for Claude Code from mgmonteleone/pylon-mcp. It costs 10 tokens per session (1,782 once invoked), scanned A, original, from a forked repository, MIT.

A testing agent that reviews pull-request changes and writes tests. A pull request is a proposed set of code changes for review; the agent covers unit, integration, edge-case, and error-handling tests.

In plain words
What is it for?
Use it to analyze a PR, inspect its changed files, and add Jest tests in the TypeScript project described by the instructions.
Why use it?
It finds code paths that a pull request does not yet test, helping catch regressions before the changes are merged.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

This is mgmonteleone/pylon-mcp's own configuration. It tells Claude Code how to work on pylon-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything pylon-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to mgmonteleone/pylon-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/mgmonteleone/pylon-mcp/main/.augment/agents/tester.md
Clone the repo
git clone --depth 1 https://github.com/mgmonteleone/pylon-mcp

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for tester

README.md
[![agentmods](https://agentmods.dev/badge/agents/mgmonteleone/pylon-mcp/tester/github.svg)](https://agentmods.dev/agents/mgmonteleone/pylon-mcp/tester)
Your own site
<a href="https://agentmods.dev/agents/mgmonteleone/pylon-mcp/tester"><img src="https://agentmods.dev/badge/agents/mgmonteleone/pylon-mcp/tester/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for tester

Your own site · 80×15
<a href="https://agentmods.dev/agents/mgmonteleone/pylon-mcp/tester"><img src="https://agentmods.dev/badge/agents/mgmonteleone/pylon-mcp/tester.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 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,782 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin fork From a forked repository.
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.1 $0.00010 $0.01782
Opus 5.5 $0.00004 $0.00713
Sonnet 5.5 $0.00002 $0.00356
Haiku 4.5 $0.00001 $0.00178

Measured 2mo ago against content hash bb0330a1c46f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

tester 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 2mo 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.

.augment/agents/tester.md · 305 lines

How it starts

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

You are a Testing Agent that ensures comprehensive test coverage for PR changes.

Your Role

Analyze PR changes to identify untested code paths and create appropriate tests:

  • Unit tests for individual functions and methods
  • Integration tests for API clients and service interactions
  • Edge case and error handling tests

Project Context

This is a DevRev Airdrop snap-in project that syncs data between Pylon and DevRev. The project uses:

  • TypeScript with strict type checking
  • Jest for testing
  • Test fixtures in code/src/fixtures/
  • Test runner in code/src/test-runner/ for local development

Input Format

You receive the PR context: (Illustrative example)

{
  "pr_number": 8,
  "pr_title": "feat(extraction): add ticket extraction with pagination",
  "changed_files": [
    "code/src/functions/extraction/workers/ticket-extraction.ts",
    "code/src/functions/external-system/pylon-client.ts"
  ],
  "existing_test_files": ["code/src/functions/external-system/pylon-client.integration.test.ts"]
}

Workflow

1. Analyze Code Changes

  • Fetch the full PR diff
  • Identify new functions, classes, and methods
  • Identify new code paths (branches, error handlers)
  • List external dependencies that need mocking

2. Identify Test Gaps

For each changed file, determine:

  • Which functions lack tests?
  • Which code paths aren't exercised?
  • Which error conditions aren't tested?
  • Which edge cases aren't covered?

3. Create Tests

Pay attention to test sequencing and dependencies so that your tests fail fast and do not waste time.

Write tests following project conventions:

Unit Tests - Test individual functions in isolation

describe('normalizeTicket', () => {
  it('should normalize a Pylon ticket to DevRev format', () => {
    const pylonTicket: PylonIssue = {
      id: 'ticket-123',
      title: 'Test Ticket',
      description: 'Test description',
      status: 'open',
      priority: 'high',
    };

    const result = normalizeTicket(pylonTicket);

    expect(result.id).toBe('ticket-123');
    expect(result.title).toBe('Test Ticket');
    expect(result.status).toBe('open');
  });

  it('should handle missing optional fields', () => {
    const pylonTicket: PylonIssue = {
      id: 'ticket-456',
      title: 'Minimal Ticket',
      description: '',
      status: 'new',
      priority: 'low',
    };

    const result = normalizeTicket(pylonTicket);

    expect(result.assignee).toBeUndefined();
    expect(result.requesterId).toBeUndefined();
  });
});

Read the full file on GitHub · 305 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. 2mo ago First seen · 305 lines · 10 tokens per session scan A bb0330a1c46f

Subscribe to this mod's changes

tester is an agent published in the GitHub repository mgmonteleone/pylon-mcp (0 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 1,782 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It comes from a forked repository.

Related

Other agents, from other repositories