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.
npx agentmods add agents/mgmonteleone/pylon-mcp/foremangit clone --depth 1 https://github.com/mgmonteleone/pylon-mcpWrote 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.
[](https://agentmods.dev/agents/mgmonteleone/pylon-mcp/foreman)<a href="https://agentmods.dev/agents/mgmonteleone/pylon-mcp/foreman"><img src="https://agentmods.dev/badge/agents/mgmonteleone/pylon-mcp/foreman.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00015 | $0.02108 |
| Opus 5 | $0.00008 | $0.01054 |
| Sonnet 5 | $0.00003 | $0.00422 |
| Haiku 4.5 | $0.00002 | $0.00211 |
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 4d 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.
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
-
Fetch Issue Context:
- Get the GitHub issue details via MCP,
ghtool or API - Parse issue body for referenced issues (
#123,Closes #456) - Fetch GitHub's linked issues/PRs
- Build a complete picture of requirements
- Get the GitHub issue details via MCP,
-
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.
-
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 }
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.
- 4d ago First seen · 263 lines · 15 tokens per session scan A a7c92022ca83
foreman is an agent published in the GitHub repository mgmonteleone/pylon-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 2,108 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
speckit.squad.status
Show alignment between your spec, tasks, and Squad agents.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…