Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add anilcancakir/claude-code-plugin/plugin install acWrote 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/anilcancakir/claude-code-plugin/setup-coding)<a href="https://agentmods.dev/commands/anilcancakir/claude-code-plugin/setup-coding"><img src="https://agentmods.dev/badge/commands/anilcancakir/claude-code-plugin/setup-coding/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/commands/anilcancakir/claude-code-plugin/setup-coding"><img src="https://agentmods.dev/badge/commands/anilcancakir/claude-code-plugin/setup-coding.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.00020 | $0.01678 |
| Opus 5.5 | $0.00008 | $0.00671 |
| Sonnet 5.5 | $0.00004 | $0.00336 |
| Haiku 4.5 | $0.00002 | $0.00168 |
Grade A, and why
setup-coding 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup My Coding Style
You are orchestrating an interactive session to build a personalized coding style skill. Analyze the developer's existing projects, interview them about preferences, then generate a skill at ~/.claude/skills/my-coding/ using skill-creator.
Core Principles
- Observe before asking: Extract patterns from code first, then confirm with the developer
- Concreteness over abstraction: Every rule must have a code example showing correct vs incorrect
- Progressive depth: Start with formatting, then architecture, then philosophy
- Respect existing style: Codify what the developer already does, not impose new standards
Phase 1: Discovery
Goal: Identify representative projects to analyze
- If $ARGUMENTS is a path → use as first project
- Ask for 1-3 project paths representing best coding style:
- "Which projects best represent your coding standards?"
- "Include projects in different languages if you work across stacks"
- If no paths provided → skip to Phase 3 (pure interview mode)
- Verify each path exists via Bash (
test -d)
Phase 2: Project Analysis
Goal: Extract coding patterns from existing projects
- For each project (max 3), use Glob, Grep, and Read directly in the main context — no subagents. Extract:
- Naming: File, class, method, variable conventions
- Structure: Directory layout, module boundaries, layering
- Formatting: Indentation, line width, trailing commas, multi-line style
- Types: Type annotations, generics, strict typing level
- Documentation: Docblock style, comment patterns, step numbering
- Testing: Framework, naming convention, TDD indicators, fixture strategy
- Error handling: Try/catch patterns, error propagation style
- Imports: Organization, grouping, barrel files
- Architecture: DI approach, service patterns, repository patterns Sampling: read 5-10 representative source files per project; prefer recently-modified files in core directories.
- Detect languages and frameworks from config files:
composer.json→ PHP/Laravelpubspec.yaml→ Dart/Flutterpackage.json→ Node/TypeScriptpyproject.toml/requirements.txt→ Python
- Synthesize findings into a unified style profile with concrete examples
- Present: "Here's what I found in your projects — let me know what's accurate and what to adjust"
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 · 180 lines · 20 tokens per session scan A d32da14a4769
setup-coding is a command published in the GitHub repository anilcancakir/claude-code-plugin (2 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 1,678 once invoked, about $0.0001 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-31.
Other commands, from other repositories
perf-difficult-conversation
Three-conversations framework rehearsal (Stone/Patton/Heen — Harvard Negotiation Project) for high-stakes conversations — termination, demotion, hard feedback, conflict surfacing. Produces three-conversations breakdown (what-happened / feelings / identity), conversation script with multiple opening choices, SCARF…
culture-onboarding-90
Design a 90-day onboarding architecture for a role. First day (psychological safety + belonging activation), first week (relationship + role context + early wins), first month (skill ramp + integration + baseline), first quarter (autonomous performance + cultural integration check). Written-first elements for…
perf-coaching-protocol
Generate a 60-minute solution-focused + CBT-grounded coaching session script for a manager-as-coach engagement. Coaches use questions, not advice. Produces session structure (check-in → focus → scaling → exception-finding → small-step → close), follow-up prompts, and the manager-as-coach training notes that name the…
reclaim-knowledge
Organize scattered professional material into a domain-based second-brain architecture. Maps existing sources (Canva, Drive, local folders, Notion, screenshots) to functional domains. Non-technical-friendly — produces folder structure + drag-and-drop instructions, not CLI commands.
design-regimen
Design an integrated weekly regimen — training, nutrition, sleep, stress, recovery — matched to the person's actual life. Composes with gym-training-expert and health-nutrition-expert for domain detail. Produces a sustainable architecture, not an extreme program. Not medical advice.
hire-calibrate
Run the pre-loop calibration session — 60 minutes with ≥3 raters, review the rubric, score 2 anchor candidates the team has previously seen, surface inter-rater drift, agree on hire-bar examples. The calibration session itself is the deliverable. Without it, the loop runs on uncalibrated rulers. Per Project Oxygen …