agentmods.dev

software_development_department: Instructions file for Claude Code

CLAUDE.md

software_development_department CLAUDE.md is an instructions file for Claude Code from tranhieutt/software_development_department. It costs 1,052 tokens per session, scanned A, original, MIT.

A set of project instructions for managing software work through specialized coding agents. It defines rules for questions, decisions, drafts, approvals, file changes, risk levels, and Git operations.

In plain words
What is it for?
Use it to guide Claude Code work in a software development department, including approvals, risk assessment, repository checks, and coordination between specialist agents.
Why use it?
It gives a team a consistent way to control agent-led development and limits unapproved edits or commits. It also documents how agents should work within the project's architecture and process.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions subagents; mentions Claude Code.

This is tranhieutt/software_development_department's own configuration. It tells Claude Code how to work on software_development_department itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything software_development_department configures →

not rated 74repo 5mo ago A scan 1,052 tokens original MIT
View source ↗ tranhieutt/software_development_department
Reuse

Borrowing it

Nothing to install: this file belongs to tranhieutt/software_development_department. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/tranhieutt/software_development_department/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/tranhieutt/software_development_department

Made for: Claude Code.

Wrote 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.

agentmods badge for software_development_department CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/tranhieutt/software_development_department/claude-md/github.svg)](https://agentmods.dev/instructions/tranhieutt/software_development_department/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/tranhieutt/software_development_department/claude-md"><img src="https://agentmods.dev/badge/instructions/tranhieutt/software_development_department/claude-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.

agentmods 80×15 button for software_development_department CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/tranhieutt/software_development_department/claude-md"><img src="https://agentmods.dev/badge/instructions/tranhieutt/software_development_department/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,052 This file is loaded in full into every session.
When invoked 1,052 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01052 $0.01052
Opus 5.5 $0.00421 $0.00421
Sonnet 5.5 $0.00210 $0.00210
Haiku 4.5 $0.00105 $0.00105

Measured 2mo ago against content hash 0fa8954500cc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

software_development_department CLAUDE.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 2mo 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.

CLAUDE.md · 75 lines

How it starts

The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Claude Code Software Development Department

Software development managed through specialized Claude Code subagents. Each agent owns a specific domain, enforcing separation of concerns and quality.

🚨 CRITICAL RULES (Must obey on every turn)

  • NO AUTOPILOT: Every task follows Question -> Options -> Decision -> Draft -> Approval.
  • CONFIRM BEFORE PROACTIVE WRITES: If the agent decides to create/edit a file outside the explicitly requested scope, MUST ask "May I write this to [filepath]?". If the user explicitly named the file or acceptEdits mode is active, skip the question.
  • NO COMMITS WITHOUT PERMISSION: Multi-file changes require explicit approval for the full changeset.
  • GIT SNAPSHOT WARNING: The Internal Git status is a STALE SNAPSHOT! You MUST run git status or git diff via BashTool before making git operations or tracking git state.
  • SAFETY TIERS & RISK ASSESSMENT: Before editing code or executing commands, assign a Risk Tier (Low: reversible; Medium: shared code, needs rollback plan; High: destructive/prod, requires explicit approval).
  • TOOL CONSTRAINTS (READ BEFORE WRITE/EDIT): You MUST read a file's contents before writing to or editing it. For edits, strictly adhere to string replacement uniqueness constraints.
  • ANNOTATION PROTOCOL: When you discover unexpected API behavior, undocumented caveats, version bugs, or non-obvious workarounds — immediately add a dated entry to .claude/memory/annotations.md via /annotate. Do NOT wait to be asked. Knowledge that is not persisted is lost.

🧭 Implicit Workflow Commands (Process Shields)

If the user invokes these short commands, or if the task context implies them, YOU MUST trigger the corresponding skill:

  • /plan: ALWAYS trigger the planning-and-task-breakdown skill first for complex epics. Output an atomic markdown task checklist. Do NOT write code yet.
  • /spec: ALWAYS trigger the spec-driven-development skill before writing logic for a task. Secure explicit blueprint/architecture approval from the user.
  • /tdd: ALWAYS trigger the test-driven-development skill when writing the source. Write failing tests, check CMD outputs (🔴 RED), implement, and pass (🟢 GREEN). Never claim success without terminal test logs.
  • /context or /memory: ALWAYS trigger the context-engineering skill. Diagnose context stuffing, optimize persistent vs episodic knowledge, and enforce the Research-Plan-Reset-Implement cycle using mcp_supermemory tools.
  • /diagnose: ALWAYS trigger the diagnose skill for complex, non-obvious failures. Use sequential Investigator -> Verifier -> Solver logic.
  • /vertical-slice: ALWAYS trigger the vertical-slicing skill when planning fullstack features. Divide work into functional end-to-end units.
  • /ui-spec: ALWAYS trigger the ui-spec skill. Transform PRDs and prototypes into rigorous technical UI specifications with state matrices.

Read the full file on GitHub · 75 lines

Changes

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.

  1. 2mo ago First seen · 75 lines · 1,052 tokens per session scan A 0fa8954500cc

Subscribe to this mod's changes

software_development_department CLAUDE.md is an instructions file published in the GitHub repository tranhieutt/software_development_department (74 stars, last pushed 5mo ago), licensed MIT. It adds 1,052 tokens to every session, about $0.0042 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-09-03.

Building agentsProject managementantigravity-skillsbrainstormingclaudeclaude-skillsharness-engineeringhuman-in-the-loop
Related

software_development_department CLAUDE.md compared with instructions from other repositories

software_development_department CLAUDE.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
software_development_department CLAUDE.mdtranhieutt/software_development_departmentInstructions file745mo agoMITA1,052Claude Code
pudo-code-system pudo-api.instructions.mdDongDuong2001/pudo-code-systemInstructions file514d agoMITA182GitHub Copilot
pudo-code-system pudo-frontend.instructions.mdDongDuong2001/pudo-code-systemInstructions file514d agoMITA197GitHub Copilot
pudo-code-system pudo-tests.instructions.mdDongDuong2001/pudo-code-systemInstructions file514d agoMITA210GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode