Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/tranhieutt/software_development_department/code-simplificationnpx skills add tranhieutt/software_development_department --skill code-simplificationgit clone --depth 1 https://github.com/tranhieutt/software_development_departmentWhat 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 | $0.00045 | $0.01564 |
| Opus 5 | $0.00023 | $0.00782 |
| Sonnet 5 | $0.00009 | $0.00313 |
| Haiku 4.5 | $0.00005 | $0.00156 |
Grade A, and why
code-simplification 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 2d 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Simplification
Purpose
code-simplification reduces code complexity while preserving exact behavior.
It is not a feature workflow, not a bug fix workflow, and not permission for
drive-by refactors.
The goal is code that is easier to read, review, test, and maintain with the smallest safe diff.
Same behavior.
Less cognitive load.
Fresh verification evidence.
Prefer simplifications that deepen modules instead of flattening behavior across callers. A small interface hiding real complexity is valuable; a wrapper that only moves complexity around is not.
When to Use
Use this workflow when:
- The implementation is working and relevant tests pass.
- Code review flags readability, complexity, naming, duplication, or avoidable abstraction.
- The user asks to simplify, clean up, reduce complexity, or refactor without changing behavior.
- A recently changed area has nested logic, long functions, unclear names, or repeated conditionals that make future changes risky.
Do not use this workflow when:
- Behavior must change. Use
spec-driven-development,test-driven-development, orspec-evolution. - The code is not understood well enough to preserve behavior.
- There is no verification path.
- The cleanup would touch unrelated files.
- The work is a hotfix where cleanup is not required for the fix.
Position in SDD
Preferred placement:
test-driven-development -> code-simplification -> verification-before-completion
Review feedback placement:
code-review -> receiving-code-review -> code-simplification
-> verification-before-completion
Technical-debt placement:
tech-debt identifies issue -> user approves focused cleanup
-> code-simplification
If a simplification requires changing externally visible behavior, API shape,
data model, error behavior, timing, permissions, or user flow, stop and route to
spec-evolution.
Preconditions
Before editing, all must be true:
- Target scope is explicit: file(s), function(s), or review finding.
- Intended behavior is known.
- Relevant tests, build, lint, typecheck, or manual verification are known.
- The current worktree state has been checked.
- The simplification is within the approved scope.
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.
- 2d ago First seen · 213 lines · 45 tokens per session scan A 5cdf54f299f9
code-simplification is a skill published in the GitHub repository tranhieutt/software_development_department (71 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 1,564 once invoked, about $0.0002 per session on Opus 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 skills, from other repositories
brainstorming
You MUST use this before any creative work (features, products, content, strategy, systems, or behavior changes). Start by classifying what we’re brainstorming, then run thorough one-question-at-a-time discovery, propose 2–3 approaches, and converge on a validated plan/spec.
security-ownership-map
Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization. Trigger only when the user explicitly wants a security-oriented ownership or bus-factor analysis grounded in git history (for…
harness-creator
Build, audit, and improve harnesses that make AI coding agents reliable: AGENTS.md/CLAUDE.md instruction files, feature/state tracking, verification gates, scope boundaries, session handoff, memory persistence, context budgets, tool-permission safety, and multi-agent coordination. Use this whenever a coding agent is…
comet-native
Comet Native 工作流。当用户明确调用 /comet-native、要求启动或恢复 Native change，或入口路由到 Native 时使用。.
comet-design
Comet Classic 阶段 2 —— 为 change 产出深度技术 Design Doc。.
openloomi-memory
OpenLoomi Memory is the long-lived context layer of OpenLoomi — a tiered, locally-stored knowledge graph that grows on its own from your Connectors, chats, and Screen Capture. Memory is what makes Chat grounded and what Loop reads before it produces a Decision. It is always on your machine (local-first), always…