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/backendgit 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.00374 | $0.00374 |
| Opus 5 | $0.00187 | $0.00187 |
| Sonnet 5 | $0.00075 | $0.00075 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
own-planner backend.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 2d 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
Backend Instructions
Technology
- Use
C#for server-side changes. - Target
.NET 10and align with the existing code style in the edited project. - Preserve nullability annotations and existing async APIs.
Coding rules
- Prefer
async/awaitfor I/O and service operations. - Preserve cancellation token flow where applicable.
- Use dependency injection instead of direct construction when wiring services.
- Validate public method arguments early.
- Preserve structured logging patterns based on
ILogger<T>and message templates. - Avoid sync-over-async unless there is already an established pattern and it cannot be changed safely.
- Dispose async resources safely.
Layering rules
- Keep domain logic in
OwnPlanner.Domain. - Keep application orchestration, use-cases, and DTO mapping in
OwnPlanner.Application. - Keep database, filesystem, external API, and adapter concerns in
OwnPlanner.Infrastructure. - Keep HTTP, authentication, and presentation concerns in
OwnPlanner.Web.Server. - Do not move infrastructure concerns into domain or application layers.
Web server guidance
- Follow existing ASP.NET Core patterns for controllers, services, and registration.
- Preserve authentication and user-isolation behavior.
- When modifying chat-related services, preserve session behavior, async disposal, and structured logs.
- Prefer extending existing services instead of duplicating cross-cutting logic.
Change preferences
- Favor small, readable changes over broad refactors.
- Keep public APIs stable unless the task explicitly requires a contract change.
- 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.
- 2d ago First seen · 43 lines · 374 tokens per session scan A e9fe2abc750b
own-planner backend.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 374 tokens to every session, about $0.0019 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.
DotNetAnalyzer CLAUDE.md
Instructions for CartapenaBark/DotNetAnalyzer, covering claude.md, 常用命令, 构建和测试, 打包和安装 and mcp 服务器.
maui integration-tests.instructions.md
Guidance for GitHub Copilot when working with .NET MAUI integration tests.
maui android.instructions.md
Instructions for dotnet/maui, covering android platform development guidelines, common build issues, view namespace collision, android handler best practices and lifecycle management.
maui public-api.instructions.md
Instructions for dotnet/maui, covering public api surface design, api addition rules, publicapi.unshipped.txt, obsolescence and removal and visibility decisions.
maui handler-patterns.instructions.md
Instructions for dotnet/maui, covering handler mapper and property patterns, property update flow, lifecycle management, null safety in callbacks and native defaults preservation.