Borrowing it
Nothing to install: this file belongs to am-space/own-planner. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/am-space/own-planner/master/.github/instructions/backend.instructions.mdgit clone --depth 1 https://github.com/am-space/own-plannerWrote 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/am-space/own-planner/backend)<a href="https://agentmods.dev/instructions/am-space/own-planner/backend"><img src="https://agentmods.dev/badge/instructions/am-space/own-planner/backend/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/instructions/am-space/own-planner/backend"><img src="https://agentmods.dev/badge/instructions/am-space/own-planner/backend.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.00374 | $0.00374 |
| Opus 5.5 | $0.00150 | $0.00150 |
| Sonnet 5.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 2mo 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.
- 2mo 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 1mo ago), licensed MIT. It adds 374 tokens to every session, about $0.0015 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-08-31.
own-planner backend.instructions.md compared with instructions from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| own-planner backend.instructions.mdam-space/own-planner | Instructions file | 2 | 1mo ago | MIT | A | 374 | GitHub Copilot |
| plan-forge api-patterns.instructions.mdsrnichols/plan-forge | Instructions file | 6 | 2d ago | MIT | A | 2,049 | GitHub Copilot |
| plan-forge graphql.instructions.mdsrnichols/plan-forge | Instructions file | 6 | 2d ago | MIT | A | 2,243 | GitHub Copilot |
| plan-forge errorhandling.instructions.mdsrnichols/plan-forge | Instructions file | 6 | 2d ago | MIT | A | 1,113 | GitHub Copilot |
| graftcode graftcode-dotnet.instructions.mdgrft-dev/graftcode | Instructions file | 967 | 1mo ago | none | A | 7,060 | GitHub Copilot |
| vscode buildNext.instructions.mdmicrosoft/vscode | Instructions file | 195k | yesterday | MIT | A | 9,719 | GitHub Copilot |
| next.js AGENTS.mdvercel/next.js | Instructions file | 143k | yesterday | MIT | A | 7,461 | Codex, OpenCode |