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/am-space/own-planner/frontendgit clone --depth 1 https://github.com/am-space/own-plannerWhat 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.00189 | $0.00189 |
| Opus 5 | $0.00095 | $0.00095 |
| Sonnet 5 | $0.00038 | $0.00038 |
| Haiku 4.5 | $0.00019 | $0.00019 |
Grade A, and why
own-planner frontend.instructions.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 3d 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.
What it actually says
Frontend Instructions
Technology
- Use
TypeScriptandReactfor client-side changes. - Match the existing React component, context, and routing patterns.
- The client uses
Vite,React Router, andMUI; prefer existing dependencies already in the project. - Keep API types aligned with backend contracts.
Coding rules
- Prefer extending existing hooks, contexts, services, and shared types over introducing new patterns.
- Do not introduce state-management libraries unless explicitly requested.
- Keep components focused and avoid broad refactors unless required by the task.
- Match the existing styling and component composition style used in the edited area.
Change preferences
- Keep changes minimal and scoped to the requested task.
- Avoid breaking UI behavior or API contracts unless explicitly requested.
- When editing existing files, match their formatting and local conventions.
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.
- 3d ago First seen · 26 lines · 189 tokens per session scan A 7b80ca50e321
own-planner frontend.instructions.md is an instructions file published in the GitHub repository am-space/own-planner (2 stars, last pushed 4d ago), licensed MIT. It adds 189 tokens to every session, about $0.0009 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-31.
Other instructions, from other repositories
csharp-sdk copilot-instructions.md
Copilot instructions for modelcontextprotocol/csharp-sdk, covering copilot instructions for mcp c# sdk, github interactions, commits and pushes, ai-generated content disclosure and critical: always build and test.
mcp-docs copilot-instructions.md
Instructions for la-rebelion/mcp-docs, covering project coding standards for typescript and react, typescript guidelines and react guidelines.
hapi-cli-website copilot-instructions.md
Copilot instructions for la-rebelion/hapi-cli-website, covering project coding standards for typescript and react, typescript guidelines, react guidelines and refactoring guidelines.
frontend-stack-blueprint CLAUDE.md
Instructions for barrosohub/frontend-stack-blueprint, covering frontend stack blueprint v2.0.0, the stack (use for every project), architecture (mandatory — apply to all code), universal governance protocol (technology-agnostic) and production reliability (mandatory by applicable profile).
ssd-ai typescript-mcp-server.instructions.md
Instructions for building Model Context Protocol (MCP) servers using the TypeScript SDK.
ssd-ai typescript-5-es2022.instructions.md
Guidelines for TypeScript Development targeting TypeScript 5.x and ES2022 output.