Borrowing it
Nothing to install: this file belongs to gsd-build/get-shit-done. 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/gsd-build/get-shit-done/main/AGENTS.mdgit clone --depth 1 https://github.com/gsd-build/get-shit-doneWrote 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/gsd-build/get-shit-done/agents-md)<a href="https://agentmods.dev/instructions/gsd-build/get-shit-done/agents-md"><img src="https://agentmods.dev/badge/instructions/gsd-build/get-shit-done/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/gsd-build/get-shit-done/agents-md"><img src="https://agentmods.dev/badge/instructions/gsd-build/get-shit-done/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.00739 | $0.00739 |
| Opus 5.5 | $0.00296 | $0.00296 |
| Sonnet 5.5 | $0.00148 | $0.00148 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
get-shit-done 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Active Discussions
For current work on Grok Build compatibility and multi-runtime synchronization across Grok Build, Claude Code, Gemini CLI, and Codex, see:
docs/discussions/grok-build-support-2026-05.md
Project Structure & Module Organization
This repository ships GSD as a Node.js CLI and SDK. Root package entry points live in bin/, scripts in scripts/, runtime hooks in hooks/, command definitions in commands/gsd/, and workflow/template content in get-shit-done/. Agent role files are in agents/; docs are in docs/; logos and terminal images are in assets/. Root tests are in tests/*.test.cjs. The TypeScript SDK is isolated under sdk/, with source and Vitest tests in sdk/src/.
Build, Test, and Development Commands
Use Node.js >=22.
npm install: install root dependencies.npm test: builds the SDK first, then runs rootnode:testsuites viascripts/run-tests.cjs.npm run test:coverage: runs root tests withc8and enforces 70% line coverage for included CommonJS library files.npm run build:hooks: rebuilds generated hook artifacts.npm run build:sdk: installs SDK dependencies and builds TypeScript.cd sdk && npm test: runs SDK Vitest unit and integration projects.cd sdk && npm run build: type-checks and emitssdk/dist/.
Coding Style & Naming Conventions
Match the existing style in the edited area. Root JavaScript is CommonJS, generally strict-mode, two-space indentation, semicolons, const/let, and node: imports for built-ins. SDK code is strict TypeScript using ESM/NodeNext. Keep command, workflow, and test filenames kebab-case, for example commands/gsd/plan-phase.md and tests/bug-2396-makefile-test-priority.test.cjs. Agent files use gsd-*.md. Avoid unrelated formatting and unnecessary dependencies.
Testing Guidelines
Root tests use Node’s built-in node:test and node:assert/strict; do not add Jest, Mocha, or Chai. Prefer helpers from tests/helpers.cjs for temporary projects, cleanup, and CLI execution. Name root tests *.test.cjs; run one with node --test tests/name.test.cjs. SDK tests use Vitest with *.test.ts for unit tests and *.integration.test.ts for integration tests.
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 · 42 lines · 739 tokens per session scan A 9b4210dcd0ff
get-shit-done AGENTS.md is an instructions file published in the GitHub repository gsd-build/get-shit-done (64,213 stars, last pushed 4mo ago), licensed MIT. It adds 739 tokens to every session, about $0.0030 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-30.
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.