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 instructions/mukul-mehta/routeup/agents-mdgit clone --depth 1 https://github.com/mukul-mehta/routeupWrote 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/instructions/mukul-mehta/routeup/agents-md)<a href="https://agentmods.dev/instructions/mukul-mehta/routeup/agents-md"><img src="https://agentmods.dev/badge/instructions/mukul-mehta/routeup/agents-md.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.00778 | $0.00778 |
| Opus 5 | $0.00389 | $0.00389 |
| Sonnet 5 | $0.00156 | $0.00156 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade A, and why
routeup AGENTS.md 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file tells AI agents how to work in the routeup repository.
Project Context
routeup is a Go CLI and networking tool that gives local services stable HTTPS route names and can expose those routes publicly through a self-hostable server.
Core docs:
PLAN.mdrecords product and architecture decisions.docs/ARCHITECTURE.mdexplains the system design.docs/ENGINEERING-STANDARDS.mddefines code quality rules.docs/MILESTONES.mddefines implementation phases.
Read those docs before changing implementation plans or writing code.
Collaboration Rule
The owner wants to write the implementation code personally.
Default agent behavior:
- Do not generate large implementation slices unless explicitly asked.
- Prefer plans, interfaces, test outlines, review comments, and debugging help.
- When asked to implement, make the smallest correct change for the current milestone only.
- Do not pull future milestone work into the current slice.
- Keep docs and code behavior aligned.
Good assistance examples:
Review my route parser.
Suggest tests for this registry behavior.
Help me debug this tunnel cancellation issue.
Design the local agent API shape.
Update docs for this command decision.
Bad assistance examples:
Implement the whole tunnel stack without being asked.
Add a plugin system because it might be useful later.
Introduce a database before persistence needs are proven.
Recommended Go Skills (Optional)
The following Go skills come from samber/cc-skills-golang. They sharpen agent guidance on Go-specific topics. They are optional — if your agent environment does not have them installed, skip them and rely on standard Go practices and the engineering rules in docs/ENGINEERING-STANDARDS.md.
When working on Go code, load any installed skills below before giving implementation advice.
Always relevant when available:
golang-how-togolang-code-stylegolang-error-handlinggolang-safetygolang-documentation
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 · 112 lines · 778 tokens per session scan A 4eceb3f5e8eb
routeup AGENTS.md is an instructions file published in the GitHub repository mukul-mehta/routeup (43 stars, last pushed 11d ago), licensed MIT. It adds 778 tokens to every session, about $0.0039 per session on Opus 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-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.