Borrowing it
Nothing to install: this file belongs to Federico-Anastasi/DYLA-ai. 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/Federico-Anastasi/DYLA-ai/main/AGENTS.mdgit clone --depth 1 https://github.com/Federico-Anastasi/DYLA-aiWrote 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/federico-anastasi/dyla-ai/agents-md)<a href="https://agentmods.dev/instructions/federico-anastasi/dyla-ai/agents-md"><img src="https://agentmods.dev/badge/instructions/federico-anastasi/dyla-ai/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/federico-anastasi/dyla-ai/agents-md"><img src="https://agentmods.dev/badge/instructions/federico-anastasi/dyla-ai/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.02557 | $0.02557 |
| Opus 5 | $0.01278 | $0.01278 |
| Sonnet 5 | $0.00511 | $0.00511 |
| Haiku 4.5 | $0.00256 | $0.00256 |
Grade A, and why
DYLA-ai 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 10d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- DYLA-ai CLAUDE.md — 92% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dyla — instructions for the agent
What this is
Dyla is a local workspace where you help someone carry a project from the first meeting to the final handover. Everything you produce is a file on their disk.
The shape of the work, when a project follows the whole arc:
meetings → brief → validation with the client
→ estimate → dev tasks → schedule
→ build → test plan → handover → maintenance
Not every project uses all of it. Someone may only ever want a meeting write-up, and that is a complete use of Dyla, not a partial one.
Where you are running
Dyla runs you either on a local model on the user's machine (the default) or on Codex Sonnet through the cloud. You cannot tell which from inside, and you do not need to — but one rule follows from it:
Never spawn subagents. On the local profile the Task tool is switched off entirely, so the attempt simply fails; on the cloud profile it would work, and then the same skill would behave differently on the two. Do the work in this conversation. If a task is too big for one turn, split it into turns and say what you are doing between them.
Your tools are fewer than you may expect, on purpose. Orchestration, scheduling, git worktrees and notebooks are switched off: a tool that is disabled does not enter the prompt at all, and carrying definitions nobody uses costs prefill on every single turn. What is left is what the work needs — read, write, edit, search the filesystem, run commands, use skills, keep a todo list — plus the web.
To search the web, use mcp__web__*. The built-in WebSearch is off on the local
profile because it reaches servers a local model cannot get to, and returns nothing.
Prefer mcp__web__research: it searches and hands back the top pages already extracted,
in one call, instead of a list of links that costs two more turns to follow.
How you work here
One skill, one deliverable
Skills live in .Codex/skills/. Each writes or updates exactly one document, and each
carries its own protocol — read it and follow it rather than improvising.
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.
- 10d ago First seen · 193 lines · 2,557 tokens per session scan A 798e07f30319
DYLA-ai AGENTS.md is an instructions file published in the GitHub repository Federico-Anastasi/DYLA-ai (2 stars, last pushed 1mo ago), licensed MIT. It adds 2,557 tokens to every session, about $0.0128 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
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.