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 commands/ww-w-ai/bkit-claude-code/output-style-setupgit clone --depth 1 https://github.com/ww-w-ai/bkit-claude-codeWrote 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/commands/ww-w-ai/bkit-claude-code/output-style-setup)<a href="https://agentmods.dev/commands/ww-w-ai/bkit-claude-code/output-style-setup"><img src="https://agentmods.dev/badge/commands/ww-w-ai/bkit-claude-code/output-style-setup.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 | $0.00078 | $0.00454 |
| Opus 5 | $0.00039 | $0.00227 |
| Sonnet 5 | $0.00016 | $0.00091 |
| Haiku 4.5 | $0.00008 | $0.00045 |
Grade A, and why
output-style-setup 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 5d 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
Output Style Setup
bkit의 Output Style을 설치합니다.
Available Styles
| Style | Recommended For | Description |
|---|---|---|
| bkit-learning | Starter | 학습 모드 - PDCA를 배우며 개발 |
| bkit-pdca-guide | Dynamic | PDCA 워크플로우 가이드 + 자동 체크리스트 |
| bkit-enterprise | Enterprise | CTO 관점 아키텍처/보안/성능 분석 |
| bkit-pdca-enterprise | Enterprise | PDCA + CTO 통합 (가장 상세) |
Instructions
Ask the user where to install using AskUserQuestion:
Option 1: Project level (current project only)
- Copy from
${CLAUDE_PLUGIN_ROOT}/output-styles/*.mdto.claude/output-styles/ - Best for: project-specific style preference
Option 2: User level (all projects)
- Copy from
${CLAUDE_PLUGIN_ROOT}/output-styles/*.mdto~/.claude/output-styles/ - Best for: consistent style across all projects
Setup Steps
- Ask user: project level or user level installation
- Create target directory if not exists
- Copy all 4 output style files to target
- Confirm installation with file list
- Suggest running
/output-styleto activate
Post-Setup
After copying, inform user:
- Use
/output-styleto select from the installed styles - Recommended style based on project level detection
- Styles can be changed anytime during session
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.
- 5d ago First seen · 59 lines · 78 tokens per session scan A 33cfd7583029
output-style-setup is a command published in the GitHub repository ww-w-ai/bkit-claude-code (595 stars, last pushed 19d ago), licensed Apache-2.0. It adds 78 tokens to every session and 454 once invoked, about $0.0004 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 commands, from other repositories
sp.reverse-engineer
Reverse engineer a codebase into SDD-RI artifacts (spec, plan, tasks, intelligence).
sp.checklist
Generate a custom checklist for the current feature based on user requirements.
sp.clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
sp.specify
Create or update the feature specification from a natural language feature description.
sp.git.commit_pr
An autonomous Git agent that intelligently executes git workflows. Your task is to intelligently executes git workflows to commit the work and create PR.
sp.implement
Execute the implementation plan with context-aware agent routing. Routes to content-implementer for authoring tasks, general-purpose for engineering, and specialized agents for platform work.