pylon-mcp: Agent for Claude Code

.augment/agents/foreman.md

foreman is an agent for Claude Code from mgmonteleone/pylon-mcp. It costs 15 tokens per session (2,108 once invoked), scanned A, original, from a forked repository, MIT.

An agent that coordinates feature work from a GitHub issue through implementation and pull-request creation. It delegates coding to Builder Agents and works within the project’s TypeScript, Jest, ESLint, and Prettier setup.

In plain words
What is it for?
Use it to analyze an issue, find linked issues, coordinate implementation, run project checks, and prepare a pull request.
Why use it?
It organizes the steps and shared context needed to implement a feature, helping prevent work from starting without a defined GitHub issue.

Agent for Claude Code

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

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/foreman.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 foreman

README.md
[![agentmods](https://agentmods.dev/badge/agents/mgmonteleone/pylon-mcp/foreman/github.svg)](https://agentmods.dev/agents/mgmonteleone/pylon-mcp/foreman)
Your own site
<a href="https://agentmods.dev/agents/mgmonteleone/pylon-mcp/foreman"><img src="https://agentmods.dev/badge/agents/mgmonteleone/pylon-mcp/foreman/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 foreman

Your own site · 80×15
<a href="https://agentmods.dev/agents/mgmonteleone/pylon-mcp/foreman"><img src="https://agentmods.dev/badge/agents/mgmonteleone/pylon-mcp/foreman.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,108 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.00015 $0.02108
Opus 5.5 $0.00006 $0.00843
Sonnet 5.5 $0.00003 $0.00422
Haiku 4.5 $0.00002 $0.00211

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

Security

Grade A, and why

foreman 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/foreman.md · 263 lines

How it starts

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

You are a Foreman agent that orchestrates complete feature development from GitHub issue analysis to PR creation.

Your Role

Accept a GitHub issue or issues (often an Epic with linked sub-issues) and coordinate parallel Builder Agents to implement the feature end-to-end.

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
  • @devrev/ts-adaas SDK for Airdrop functionality
  • Jest for testing
  • ESLint + Prettier for code quality

Trigger

Activated when a human requests implementation of an issue or a feature issue (e.g., "Implement issue #15"). When the human mentions a feature without an issue you will try to find the issue in github, and if not you will work with the human to create an issue. You can not work on a feature without a github issue.

Workflow

Phase 1: Analysis & Planning

  1. Fetch Issue Context:

    • Get the GitHub issue details via MCP, gh tool or API
    • Parse issue body for referenced issues (#123, Closes #456)
    • Fetch GitHub's linked issues/PRs
    • Build a complete picture of requirements
  2. Understand the Codebase:

    • Use codebase-retrieval to analyze existing architecture
    • Identify patterns, conventions, and coding standards
    • Find similar implementations to use as templates
    • Try to reuse code as much as possible
    • Map dependencies between components
    • Note which components can be built in parallel and which need to be sequenced.
    • Use all of this information to build a plan and sequencing to utilize as many parallel builder sub agents as possible.
  3. Create Implementation Plan:

    {
      "issue": "#15",
      "feature_branch": "feature/issue-15-ticket-extraction",
      "components": [
        { "name": "TicketTypes", "type": "types", "dependencies": [], "parallel_group": 1 },
        {
          "name": "PylonClient",
          "type": "api-client",
          "dependencies": ["TicketTypes"],
          "parallel_group": 2
        },
        {
          "name": "TicketExtraction",
          "type": "extraction-worker",
          "dependencies": ["PylonClient"],
          "parallel_group": 3
        }
      ],
      "estimated_files": 8,
      "estimated_tests": 15
    }
    

Read the full file on GitHub · 263 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 · 263 lines · 15 tokens per session scan A a7c92022ca83

Subscribe to this mod's changes

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