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/51ck/frontier-mcp/issue-trackergit clone --depth 1 https://github.com/51ck/frontier-mcpWhat 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.00000 | $0.02355 |
| Opus 5 | $0.00000 | $0.01177 |
| Sonnet 5 | $0.00000 | $0.00471 |
| Haiku 4.5 | $0.00000 | $0.00235 |
Grade A, and why
issue-tracker 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 yesterday.
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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue tracker — FrontierMCP and file fallback
Issues and specs live as markdown under .scratch/. Vocabulary is defined in the project's
CONTEXT.md when present — Effort, Board, Header doc, Map, Spec, Ticket, Edge, Frontier.
When FrontierMCP (server name frontier) is loaded in your session, use the tools below. They
own the schema, compute the graph, and answer orientation questions for a fraction of the token cost
of reading every Ticket file. When it is not loaded, follow the File conventions
literally — the same files, the same fields, written by hand.
Read this document once at setup. In Cursor it is also available as MCP resource frontier://tracker-doc.
Workspace
FrontierMCP resolves which repository it serves on every call:
- An explicit
rootargument on the call. - The
FRONTIER_ROOTenvironment variable. - The server process working directory, walked upward to the nearest directory containing a
.scratch/directory, or.gitin either form — a git worktree and a submodule carry.gitas a file, and each is its own workspace rather than part of the repository enclosing it.
Register FrontierMCP once at user scope. Opening a project is the only per-repo setup step — no
.cursor/mcp.json entry is required in each repository.
The working directory is the one your client launched the server in, and it is fixed for the
session. Moving to another worktree mid-session does not retarget it: pass root on the call, set
FRONTIER_ROOT, or restart the server. A worktree whose branch carries no .scratch/ of its own
reports no Efforts — that is the worktree being served correctly, not the tracker going missing.
Every call that writes opens with root: <path>, naming the repository it just changed. Read it
— a Ticket id is not repo-unique, so T10 updated looks the same whichever repository answered, and
this line is the only part of the result that tells you. Reads do not carry it, and neither do the
read paths of write-capable tools: edit_map with no section fields, spec with no content, and
migrate_effort with preview.
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.
- yesterday First seen · 169 lines · 0 tokens per session scan A c9c0d4b69b1b
issue-tracker is an agent published in the GitHub repository 51ck/frontier-mcp (0 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,355 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.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.