Borrowing it
Nothing to install: this file belongs to joshidikshant/devsquad. 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/joshidikshant/devsquad/main/AGENTS.mdgit clone --depth 1 https://github.com/joshidikshant/devsquadWrote 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/joshidikshant/devsquad/agents-md)<a href="https://agentmods.dev/instructions/joshidikshant/devsquad/agents-md"><img src="https://agentmods.dev/badge/instructions/joshidikshant/devsquad/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/joshidikshant/devsquad/agents-md"><img src="https://agentmods.dev/badge/instructions/joshidikshant/devsquad/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.00335 | $0.00335 |
| Opus 5.5 | $0.00134 | $0.00134 |
| Sonnet 5.5 | $0.00067 | $0.00067 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
devsquad 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 17d 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.
What it actually says
Working on DevSquad
Read CONTRIBUTING.md before changing code. Run
bash test/run.sh before every commit; core changes also need the relevant
offline Python tests. Preserve the existing Bash 3.2 and optional-jq contracts.
Continuing the engineering-team build
This build is already underway. After a usage limit, interrupted session or handoff, read these files before starting work:
- RESUME.md: latest checkpoint, verified results, open findings and exact next action.
- backlog.json: milestone status and evidence.
- SOL-HANDOFF.md: the full authorized delivery scope and acceptance criteria.
Compare the recovery note with git status and recent commits; retain work
newer than the note. Continue on codex/engineering-team unless the user
directs otherwise. Do not restart the architecture exercise or discard
implementation to return to main.
Checkpoint coherent partial work and update RESUME.md before long probes or handoffs. Record failures and incomplete gates truthfully. Finish a pause with a clean tree; never use a stash as the recovery mechanism. Keep raw provider diagnostics and credentials outside tracked evidence.
Usage limits do not authorize buying credits, redeeming reset credits, using a paid API fallback or changing global AI settings. The saved artifacts must allow the next session to resume without relying on conversation memory.
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.
- 17d ago First seen · 32 lines · 335 tokens per session scan A 4a0a0e65d9b2
devsquad AGENTS.md is an instructions file published in the GitHub repository joshidikshant/devsquad (7 stars, last pushed 17d ago), licensed MIT. It adds 335 tokens to every session, about $0.0013 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-10-03.
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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.