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 skills add tranhieutt/software_development_department --skill agent-stylegit clone --depth 1 https://github.com/tranhieutt/software_development_departmentWrote 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/skills/tranhieutt/software_development_department/agent-style)<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/agent-style"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/agent-style.svg" alt="Measured on agentmods" 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.00055 | $0.00612 |
| Opus 5 | $0.00028 | $0.00306 |
| Sonnet 5 | $0.00011 | $0.00122 |
| Haiku 4.5 | $0.00006 | $0.00061 |
Grade A, and why
agent-style 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 8d 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.
What it actually says
Agent Style
Portable SDD wrapper for the vendored agent-style v0.3.5 rule pack.
This skill exists so Agent-Style support moves with .claude/skills/ when SDD
is applied to another project. It does not enable global writing style, does not
edit AGENTS.md or CLAUDE.md, and does not replace style-review.
Bundled Source
- Rules:
references/RULES.md - Upstream pin:
references/UPSTREAM.md - Attribution:
references/NOTICE.md - Detector notes:
references/rule-detectors.md - Revision prompt:
references/revision-prompt.md
Retain references/NOTICE.md when copying or redistributing this skill.
Install Check
When asked whether Agent-Style is available in a target project, verify:
.claude/skills/agent-style/SKILL.mdexists..claude/skills/agent-style/references/RULES.mdexists..claude/skills/style-review/SKILL.mdpoints to the bundled agent-style references, not a required repository-level.agent-style/directory.
If the target project still uses .agent-style/ directly, migrate by copying
this entire skill folder and updating style-review source paths.
CLI Check
For deterministic audits, check:
agent-style --version
If missing, report:
agent-style deterministic audit unavailable: `agent-style` CLI is not on PATH. Bundled rules remain available for semantic review through `.claude/skills/agent-style/references/`.
Do not install dependencies unless the user asks.
Audit Routing
For file review, use style-review. This skill supplies the portable rule pack;
style-review supplies the review workflow, audit command, polish invariants,
and completion evidence.
Use this skill directly only for:
- Checking whether Agent-Style travels with SDD apply/sync.
- Reading the pinned rules or upstream metadata.
- Migrating an older
.agent-style/-based repo into.claude/skills.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 71 lines · 55 tokens per session scan A 6908f1504fc1
agent-style is a skill published in the GitHub repository tranhieutt/software_development_department (72 stars, last pushed 3mo ago), licensed MIT. It adds 55 tokens to every session and 612 once invoked, about $0.0003 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
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
database-migrations
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).
flutter-ui
Build Flutter UI from Figma MCP or image input. Scans src for design tokens (colors, sizes, text styles), existing components, and naming conventions before writing a single line of code. Never hard-codes values.
serena
Serena code intelligence — LSP-powered symbol navigation, diagnostics, and targeted code surgery. Activate before complex refactors, cross-file analysis, or when graph tools need symbol-level depth.
analyze
Risk analysis and approach selection before planning. Use when requirements are ambiguous, approaches vary, or work touches hub/bridge nodes. Skip for typo fixes.
prototype
Build throwaway code to validate an uncertain approach before committing to a plan. Two branches — Logic (terminal state machine) or UI (multiple designs on one route with URL-param switcher). No persistence, no tests, single-command start. Use between analyze and plan when the approach itself is uncertain.