Borrowing it
Nothing to install: this file belongs to codeworksh/codework. 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/codeworksh/codework/main/AGENTS.mdgit clone --depth 1 https://github.com/codeworksh/codeworkWrote 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/codeworksh/codework/agents-md)<a href="https://agentmods.dev/instructions/codeworksh/codework/agents-md"><img src="https://agentmods.dev/badge/instructions/codeworksh/codework/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/codeworksh/codework/agents-md"><img src="https://agentmods.dev/badge/instructions/codeworksh/codework/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.01360 | $0.01360 |
| Opus 5.5 | $0.00544 | $0.00544 |
| Sonnet 5.5 | $0.00272 | $0.00272 |
| Haiku 4.5 | $0.00136 | $0.00136 |
Grade A, and why
codework 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 16d 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:
- codework CLAUDE.md — 95% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Personal Preference
TypeScript
- Never use
anyunless 100% necessary or specifically instructed. - Use effect only if the project uses effect or specifically instructed, use effect reference repository for latest architecture patterns.
Commands
- Don't run dev server commands (e.g
pnpm run dev,bun run dev) - assume it's already running. - Don't run build commands unless specifically told to.
- Focus on checking commands like
pnpm run check,bun run lintbun run typecheck, etc.
Package Managers
- Use
pnpm,vp - vite plusif the project already uses it, otherwise usepnpm - Never use
npmor `yarn
Tech Stack Preference
When uncertain, prefer: Effect, Tailwind, TypeScript, React, Clerk, TanStack, Vercel, Vite
Code Style
- Always strive for concise, simple solutions.
- If a problem can be solved in a simpler way, propose it.
- No pre-mature optimizations, propose if required.
- Use single word filename whenever possible otherwise split into kabab-case(only if no options).
General Preferences
- If asked to do too much work at once, stop and state that clearly.
- If computer use is helpful for completing or verifying work, use it.
- Avoid defensive future-facing design. This leads to pre-mature assumptions which are never true.
Maintainability
Long term maintainability is a core priority. If you add new functionality, first check if there is shared logic that can be extracted to a separate module. Duplicate logic across multiple files is a code smell and should be avoided. Don't be afraid to change existing code. Don't take shortcuts by just adding local logic to solve a problem.
Package Roles
packages/aikit- Low level SDK that provides unified LLM API for multiple LLM providers.packages/harness- Effect powered main Agent Harness application, usespackages/aikitunder the hood.packages/plugin- The published SDK third-party plugin and sandbox-driver packages build against. It owns the shared contract (plugin, tool, sandbox mount, event and settings types);packages/harnessdepends on it, never the other way round..scratch/packages- Local, ignored reference archive for packages that are no longer developed.
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.
- 16d ago Changed · +8 lines · +137 tokens per session e7783d0042c0
- 28d ago Changed · +4 tokens per session ff7850947f36
- 1mo ago Changed · +7 lines · +183 tokens per session 6317edf93d44
- 1mo ago Changed · +1 lines · +52 tokens per session 90bcce2292bc
- 1mo ago Changed · -1 lines · -22 tokens per session 1db49ee92ef5
- 1mo ago First seen · 82 lines · 1,006 tokens per session scan A a3b9934cf5c7
codework AGENTS.md is an instructions file published in the GitHub repository codeworksh/codework (24 stars, last pushed yesterday), licensed MIT. It adds 1,360 tokens to every session, about $0.0054 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).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.