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/agents-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/agents-md)<a href="https://agentmods.dev/instructions/am-space/own-planner/agents-md"><img src="https://agentmods.dev/badge/instructions/am-space/own-planner/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.01768 | $0.01768 |
| Opus 5 | $0.00884 | $0.00884 |
| Sonnet 5 | $0.00354 | $0.00354 |
| Haiku 4.5 | $0.00177 | $0.00177 |
Grade A, and why
own-planner 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to Codex (Codex.ai/code) when working with code in this repository.
Overview
OwnPlanner is an AI-powered personal planning assistant: a layered .NET 10 solution with a React + TypeScript (Vite, MUI) frontend. Users chat with a Google Gemini LLM that invokes in-process MCP-style tools to manage tasks, notes, goals, and contexts stored in per-user SQLite databases.
Common commands
Run from the repo root unless noted.
# Install/restore dependencies, then run the full local CI-equivalent verification
./scripts/setup.sh
./scripts/verify.sh
# Verify only one stack
./scripts/verify.sh --backend
./scripts/verify.sh --frontend
# Single test project, class, or method
dotnet test OwnPlanner.Application.Tests/OwnPlanner.Application.Tests.csproj
dotnet test --filter "FullyQualifiedName~OwnPlanner.Domain.Tests.SomeClass"
dotnet test --filter "DisplayName~my_test_name"
# Run the web server (auto-launches the Vite dev server via SpaProxy)
dotnet run --project OwnPlanner.Web/OwnPlanner.Web.Server # http://localhost:5079
# Run the console chat loop (type `exit` to quit)
dotnet run --project OwnPlanner.Console
Frontend (from OwnPlanner.Web/ownplanner.web.client/):
npm ci
npm run dev # Vite dev server
npm run build # tsc -b && vite build
npm run lint # eslint
CI (.github/workflows/ci.yml) uses the same scripts: scripts/setup.sh, then frontend and backend
verification. Run ./scripts/verify.sh before pushing to match both verification paths locally.
Git workflow
- Never commit directly to
master. - Before the first task commit, create or switch to a dedicated branch. Unless the user specifies
another name, use
feature/<short-description>for enhancements andfix/<short-description>for bug fixes. - Keep unrelated staged or working-tree changes out of task commits.
- Open a pull request targeting
masterwhen the work is ready for review.
Architecture
Strict clean-architecture layering; dependencies only flow inward toward the Domain. Test projects mirror each layer (*.Tests).
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 · 131 lines · 1,768 tokens per session scan A 9a1fb289cecf
own-planner AGENTS.md is an instructions file published in the GitHub repository am-space/own-planner (2 stars, last pushed 5d ago), licensed MIT. It adds 1,768 tokens to every session, about $0.0088 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
bifrost AGENTS.md
AGENTS.md instructions for maximhq/bifrost, covering agents.md — bifrost ai gateway, what is bifrost?, repository layout, go workspace and build, test & dev commands.
mcp-dotnet-samples AGENTS.md
AGENTS.md instructions for microsoft/mcp-dotnet-samples, covering agents.md - mcp .net samples, project overview, project structure and architecture, repository organization and sample components.
mcp-dotnet-samples copilot-instructions.md
Copilot instructions for microsoft/mcp-dotnet-samples, covering copilot instructions (concise) – mcp .net samples, architecture & runtime, sample-specific nuance, core conventions and adding / modifying tools.
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-router CLAUDE.md
Claude Code instructions for mcp-router/mcp-router, a project described as: A Unified MCP Server Management App (MCP Manager).
SqlAugur AGENTS.md
AGENTS.md instructions for mbentham/SqlAugur, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.