Borrowing it
Nothing to install: this file belongs to JinPLu/Teamwork. 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/JinPLu/Teamwork/main/AGENTS.mdgit clone --depth 1 https://github.com/JinPLu/TeamworkWrote 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/jinplu/teamwork/agents-md)<a href="https://agentmods.dev/instructions/jinplu/teamwork/agents-md"><img src="https://agentmods.dev/badge/instructions/jinplu/teamwork/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/jinplu/teamwork/agents-md"><img src="https://agentmods.dev/badge/instructions/jinplu/teamwork/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.00614 | $0.00614 |
| Opus 5.5 | $0.00246 | $0.00246 |
| Sonnet 5.5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
Teamwork 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Teamwork Repository
skills/ is the source of truth. Clear authorized work stays native; a named
Skill adds only the method described by its trigger. Cursor and Claude Code
adapters are optional compatibility surfaces and never block Codex work.
Working Conventions
- Change the owning
SKILL.mdbefore workflow behavior. Public docs stay outcome-focused. policy/teamwork-global.mdcarries cross-project working rules that must hold before any Skill loads, plus the minimum routing, delegation, and persistence bridge. A rule an owningSKILL.mdalready carries does not belong there, and a test must not require the same sentence in both places. Commit a change to that file separately from the release commit, carrying only the edits needed to keep the tree green, so its growth stays reviewable on its own.- Shell scripts use Bash with
set -euo pipefail, quoted variables, and arrays; everySKILL.mdfrontmatter has onlynameanddescription, whose value starts withUse when. - Agent delegation is optional unless the user explicitly requires independent work. Handoffs contain only objective, scope, settled constraints, evidence, and requested return. Missing agents never trigger Update automatically.
- Project-local Teamwork setup is one concise managed
AGENTS.mdblock. It has no document database, schema, case lifecycle, or migration gate.
Commands
- Run
./scripts/validate.shfor the small local smoke suite. Use./scripts/validate.sh --releaseonly for explicit release preparation. ./scripts/check-update.sh --readinessreports Codex install state without becoming a workflow gate.init-projectmaintains the project instruction block;updaterefreshes Codex unless another host is explicitly selected.
Releases
- Release on
mainunless the user explicitly requests another Git workflow. - VERSION consistency is checked by
./scripts/validate.sh. - A release is complete only after the requested verification, commit, tag, and GitHub Release succeed. Cursor/Claude adapters and project-local files are not release blockers.
- Keep release notes short and describe user-visible behavior rather than internal tests, gates, or version history.
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 · 51 lines · 614 tokens per session scan A 8ab7da4aab80
Teamwork AGENTS.md is an instructions file published in the GitHub repository JinPLu/Teamwork (12 stars, last pushed 1mo ago), licensed MIT. It adds 614 tokens to every session, about $0.0025 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
data-scientist copilot-instructions.md
Repository instructions for a data-science workflow in GitHub Copilot, covering datasets, statistics, and analysis files.
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).