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/dirmacs/daedra/agents-mdgit clone --depth 1 https://github.com/dirmacs/daedraWhat 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.00848 | $0.00848 |
| Opus 5 | $0.00424 | $0.00424 |
| Sonnet 5 | $0.00170 | $0.00170 |
| Haiku 4.5 | $0.00085 | $0.00085 |
Grade A, and why
daedra 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 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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
daedra — Agent Guidelines
What this is
Daedra is a web search MCP server. It gives search and fetch tools to AI agents via MCP (Model Context Protocol). Fourteen unkeyed backends run in a fallback chain. Circuit breakers and per-backend rate limits keep search reliable from any IP.
Rules for agents
- Run
cargo testbefore you change any file. All tests must pass. - The fallback chain is the core value. Do not change the backend order in
SearchProvider::auto()without a good reason. - Each backend is independent. A new backend must not change the behavior of other backends.
- The MCP server registers tools in
src/server.rs(DaedraHandler::list_tools). The handlers arehandle_web_search,handle_visit_page, andhandle_crawl_site. - Tool names:
web_search(primary),search_duckduckgo(backward-compatibility alias),visit_page,crawl_site. - The cache layer is transparent. Backends do not know that the cache exists.
- Do not hardcode paths or API keys in source code. All configuration comes from environment variables or CLI arguments.
Module map
| Path | Role |
|---|---|
src/main.rs |
CLI entry — Commands::run, CheckReporter for daedra check |
src/server.rs |
MCP server, transports, DaedraHandler tool dispatch |
src/lib.rs |
Crate root, re-exports |
src/url_classification.rs |
Data-driven URL → ContentType rules for search results |
src/tools/backend.rs |
SearchProvider, BackendHealth circuit breakers, governor keyed limiters, classified retry, aggregate failure messages |
src/tools/rss.rs |
Machine-format backends: Bing RSS, Google News RSS, HN Algolia |
src/tools/soft_block.rs |
Zero-result page classifier: genuine no-results or soft block |
src/tools/fetch.rs |
FetchClient, FetchedContent (Html/Pdf/Document/Text/Binary), dom_smoothie, infer, pdf-inspector, anydoc |
src/tools/crawl.rs |
Site crawl (sitemap + link following) |
src/tools/bing.rs, src/tools/google.rs |
HTML scraper backends |
src/tools/*.rs |
Other individual search backends |
src/cache.rs |
moka async cache layer |
src/types.rs |
Shared types; detect_language / detect_topics use data-driven tables |
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 · 49 lines · 848 tokens per session scan A afe60583a9c0
daedra AGENTS.md is an instructions file published in the GitHub repository dirmacs/daedra (13 stars, last pushed 3d ago), licensed MIT. It adds 848 tokens to every session, about $0.0042 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-30.
Other instructions, from other repositories
mcp-server-excel coverage-prevention-strategy.instructions.md
Instructions for sbroenne/mcp-server-excel, covering generated surface coverage, contract change workflow, required checks and common incomplete changes.
mcp-server-excel mcp-llm-guidance.instructions.md
Instructions for sbroenne/mcp-server-excel, a project described as: Automate real Microsoft Excel with AI via MCP Server or CLI — Power Query, DAX, VBA, PivotTables, charts, and 326 operations.
openrouter-mcp-multimodal AGENTS.md
Instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
ntfy-mcp-server AGENTS.md
Instructions for cyanheads/ntfy-mcp-server, covering developer protocol, what's next?, core rules, patterns and tool.
Plonk AGENTS.md
Instructions for ostapondo/Plonk, covering agent rules, layout, adding a module, build & verify and code style.
mcp-dockhand copilot-review.instructions.md
Instructions for strausmann/mcp-dockhand: When reviewing pull requests in this repository.