Borrowing it
Nothing to install: this file belongs to AncientiCe/palace-rs. 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/AncientiCe/palace-rs/main/AGENTS.mdgit clone --depth 1 https://github.com/AncientiCe/palace-rsWrote 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/ancientice/palace-rs/agents-md)<a href="https://agentmods.dev/instructions/ancientice/palace-rs/agents-md"><img src="https://agentmods.dev/badge/instructions/ancientice/palace-rs/agents-md/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/ancientice/palace-rs/agents-md"><img src="https://agentmods.dev/badge/instructions/ancientice/palace-rs/agents-md.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.01400 | $0.01400 |
| Opus 5.5 | $0.00560 | $0.00560 |
| Sonnet 5.5 | $0.00280 | $0.00280 |
| Haiku 4.5 | $0.00140 | $0.00140 |
Grade A, and why
palace-rs 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 1mo 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Rules
When working on this codebase, follow these rules on every task.
1. Test-Driven Development (TDD)
- Write behavioural tests first. Define the expected behaviour in tests before implementing.
- See them fail. Run the test suite and confirm the new tests fail (red).
- Implement. Write the minimum code to make the tests pass.
- See them pass. Run the test suite and confirm all tests pass (green).
Do not implement behaviour without a failing test that defines it.
2. Quality Gates on Every Task
Before considering a task done, ensure all of the following pass:
cargo fmt— code is formatted.cargo clippy --all-targets --all-features -- -D warnings— no clippy warnings or errors.cargo audit— no known security advisories in dependencies.cargo test --all-features— full test suite passes.- Pipelines pass — check pipeline steps that can be run locally and make sure they pass.
Match CI locally with the exact commands above (see .github/workflows/ci.yml).
Fix any failure before marking the task complete.
3. No Plan Markdown Files
- Do not create
.mdfiles for plans (e.g.PLAN.md,TODO.md, task plans). - Create markdown only for documentation (API, README, runbooks, etc.) when necessary.
- Keep planning in conversation, tickets, or code comments—not as standalone plan documents in the repo.
4. Internal API Discipline
- palace-rs is a CLI/MCP tool: it ships to users as compiled binaries via the Homebrew
tap, the install script, and the MCP registry
.mcpbbundle. - Internally, the crate is split into a
[lib](thePalacefacade insrc/palace.rs) and a[[bin]](src/cli.rs, behind theclifeature flag). The CLI and the MCP server (src/mcp_server.rs) both build on that internal API, so keep it clean and minimal for maintainability. - Before changing public types, functions, or module structure, consider: the CLI and MCP server call sites, SQLite schema migrations, and embedding model compatibility.
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.
- 1mo ago First seen · 121 lines · 1,400 tokens per session scan A c84ec6380435
palace-rs AGENTS.md is an instructions file published in the GitHub repository AncientiCe/palace-rs (10 stars, last pushed yesterday), licensed MIT. It adds 1,400 tokens to every session, about $0.0056 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.
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.