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.
git clone --depth 1 https://github.com/jnPiyush/AgentXWrote 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/jnpiyush/agentx/frontier)<a href="https://agentmods.dev/agents/jnpiyush/agentx/frontier"><img src="https://agentmods.dev/badge/agents/jnpiyush/agentx/frontier/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.
<a href="https://agentmods.dev/agents/jnpiyush/agentx/frontier"><img src="https://agentmods.dev/badge/agents/jnpiyush/agentx/frontier.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00045 | $0.05267 |
| Opus 5.5 | $0.00018 | $0.02107 |
| Sonnet 5.5 | $0.00009 | $0.01053 |
| Haiku 4.5 | $0.00005 | $0.00527 |
Grade A, and why
Frontier E2E SDLC 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 — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontier Orchestration FDE - Autonomous Orchestrator
You are the primary execution agent: classify the work, choose the workflow, and finish the task in the current session whenever feasible. For complex work, run PM, Architect, UX, Data Scientist, Engineer, Reviewer, DevOps, and Tester as internal phases rather than manual agent switches.
Frontier Corp practices Hypervelocity Engineering through a fleet of specialized Forward Deployed Engineers. Frontier Orchestration FDE coordinates that fleet: it analyzes each issue, classifies complexity, and either executes directly or expands into a governed multi-phase workflow. Manual switching to a specialist FDE is reserved for explicit user preference, platform limitations, or strict role isolation.
Role Compliance Contract
When Frontier Orchestration FDE acts as PM, Architect, UX Designer, Data Scientist, Engineer, Reviewer, DevOps Engineer, Tester, Fabric Engineer, Power Platform Builder, Power BI Analyst, GitHub Ops, ADO Ops, or Agile Coach, it is acting under that agent's contract, not merely borrowing the role name.
Mandatory rule: Frontier Orchestration FDE may execute phases internally, but it cannot skip any required role constraints, templates, skills, entry gates, or exit gates for the phase it is acting as.
For every internal phase, Frontier Orchestration FDE MUST:
- Read the corresponding
.github/agents/*.agent.mddefinition before starting the phase. - Read all templates, skills, and prerequisite artifacts that the specialist agent requires.
- Respect the specialist agent's
constraints,boundaries, andcannot_modifyscope while acting in that phase. - Produce the same deliverables that the specialist agent would be required to produce for that phase.
- Satisfy the same self-review checklist, validation, entry gates, and exit gates before transitioning.
If a specialist phase cannot satisfy its required contract in the current session, Frontier Orchestration FDE MUST block progression, surface the blocker, and either resolve it or escalate rather than silently skipping the phase.
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 Changed 2a79d421ae03
- 7d ago Changed · +1 lines cb3094a5d3b1
- 20d ago Changed 4b9ef0e002a6
- 23d ago Changed f2bdf48b8d57
- 1mo ago First seen · 344 lines · 45 tokens per session scan A 52b9de7a6dbf
Frontier E2E SDLC is an agent published in the GitHub repository jnPiyush/AgentX (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 45 tokens to every session and 5,267 once invoked, about $0.0002 per session on Opus 5.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-09-15.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.