Borrowing it
Nothing to install: this file belongs to Dash-096/dedalus-mcp-python. 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/Dash-096/dedalus-mcp-python/main/AGENTS.mdgit clone --depth 1 https://github.com/Dash-096/dedalus-mcp-pythonWrote 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/dash-096/dedalus-mcp-python/agents-md)<a href="https://agentmods.dev/instructions/dash-096/dedalus-mcp-python/agents-md"><img src="https://agentmods.dev/badge/instructions/dash-096/dedalus-mcp-python/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/dash-096/dedalus-mcp-python/agents-md"><img src="https://agentmods.dev/badge/instructions/dash-096/dedalus-mcp-python/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.01657 | $0.01657 |
| Opus 5.5 | $0.00663 | $0.00663 |
| Sonnet 5.5 | $0.00331 | $0.00331 |
| Haiku 4.5 | $0.00166 | $0.00166 |
Grade A, and why
dedalus-mcp-python 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 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.
This is a copy
100% identical to dedalus-mcp-python AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guidelines for Coding Agents
Dedalus MCP implements the Model Context Protocol. Spec-faithful, minimal surface.
Quick Reference
| What | Where |
|---|---|
| MCP spec | internals/references/modelcontextprotocol/ |
| Reference SDK | internals/references/python-sdk/ |
| Server core | src/dedalus_mcp/server/core.py |
| Versioning | src/dedalus_mcp/versioning.py |
| Types | src/dedalus_mcp/types/ |
| Tests | tests/ |
Before You Code
Scan wide before you write. Search for logic that already does what you need. Search for logic that could help your implementation. Understand where your contribution fits contextually within this codebase. Don't write a single line until you understand these relationships.
- Grep (or rg) the codebase for related functionality. It may already exist!
- Find the spec section for what you're implementing
- Look at similar existing code for patterns and conventions
- Identify code that your implementation should integrate with
Test-Driven Development
Write tests first. This project follows TDD. Don't implement features in a vacuum—define what "correct" looks like before you write production code.
The workflow:
-
Create or update an execspec — For any significant work, maintain a local
EXECSPEC-{topic}.mdindocs/dedalus_mcp/. This is your working document: what you're building, what invariants must hold, what's done, what's next. -
Write a failing test — Before implementing, write a test that captures an invariant from your execspec. The test should fail because the feature doesn't exist yet.
-
Make it pass — Write the minimal code to make the test pass. No more.
-
Refactor — Clean up while tests are green.
-
Repeat — Each passing test is a small victory. Accumulate these toward the full vision.
Example execspec structure:
# EXECSPEC: Elicitation Support
## Goal
Implement client-side elicitation per MCP 2025-06-18.
## Invariants
- [ ] `elicit()` raises if server doesn't advertise elicitation capability
- [ ] Timeout triggers `ElicitationTimeoutError`
- [ ] Response schema is validated against `ElicitationResult`
## Progress
- [x] Basic request/response flow
- [ ] Timeout handling
- [ ] Schema validation
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 · 192 lines · 1,657 tokens per session scan A 41c5315910e6
dedalus-mcp-python AGENTS.md is an instructions file published in the GitHub repository Dash-096/dedalus-mcp-python (0 stars, last pushed 3mo ago), licensed MIT. It adds 1,657 tokens to every session, about $0.0066 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to dedalus-mcp-python AGENTS.md, differing in 0 lines, and is treated as a copy.
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.