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-language)<a href="https://agentmods.dev/commands/anilcancakir/claude-code-plugin/setup-language"><img src="https://agentmods.dev/badge/commands/anilcancakir/claude-code-plugin/setup-language/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-language"><img src="https://agentmods.dev/badge/commands/anilcancakir/claude-code-plugin/setup-language.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.00016 | $0.01781 |
| Opus 5.5 | $0.00006 | $0.00712 |
| Sonnet 5.5 | $0.00003 | $0.00356 |
| Haiku 4.5 | $0.00002 | $0.00178 |
Grade A, and why
setup-language scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
4. Verify paths via Bash (`test -f` or `test -d`). For URLs → fetch via Bash (`curl`) How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup My Language Style
You are orchestrating an interactive session to build a personalized writing and documentation style skill. Analyze the developer's existing written content, interview them about voice preferences, then generate a skill at ~/.claude/skills/my-language/ using skill-creator.
Core Principles
- Read before profiling: Extract voice patterns from actual writing samples first
- Context-aware tone: Docs, articles, and commit messages each have different tone rules
- Capture the voice, not grammar rules: HOW the person communicates, not generic writing advice
- Preserve authenticity: Codify the developer's natural voice, not an idealized version
Phase 1: Discovery
- If $ARGUMENTS is a path → use as first sample source
- Ask for writing samples across categories:
- "Share 1-3 sources that represent your writing voice"
- Accepted formats:
- Article URLs: Published blog posts, Medium articles, dev.to posts
- Documentation paths: README files, docs/ directories, wiki pages
- File paths: Markdown files, technical guides, tutorials
- Git repos: Extract commit messages and PR descriptions automatically
- If no samples provided → skip to Phase 3 (pure interview mode)
- Verify paths via Bash (
test -fortest -d). For URLs → fetch via Bash (curl)
Phase 2: Sample Analysis
- For each sample source (max 3), use Glob, Grep, and Read directly in the main context — no subagents. Extract:
- Voice traits: Personal/formal, active/passive, sentence length average
- Opening patterns: How sections/articles/docs begin
- Transition phrases: Recurring connectors and segue patterns
- Code introductions: How code blocks are introduced and followed up
- Closing patterns: Abrupt, summary, call-to-action, or friendly
- Signature expressions: Recurring phrases, verbal tics, characteristic word choices
- Structure patterns: Section flow, heading hierarchy, list usage, callout usage
- Tone differences: How tone shifts between documentation vs. articles vs. comments
- Rhetorical devices: Questions, analogies, humor usage
- Formatting habits: Bold/italic usage, table frequency, emoji usage
- Git availability check: run
git --versionto confirm git is installed, thengit -C <path> rev-parse --git-dirto confirm the path is a git repo. If unavailable → skip commit/PR pattern extraction and note: "Git history unavailable — skipping commit style analysis." - If a git repo is provided, additionally extract:
- Commit message style (conventional commits? imperative? past tense?)
- PR description patterns
- Code comment voice
- Synthesize findings into a voice profile with direct quotes from the samples
- Present: "Here's your writing voice profile — confirm what's accurate and flag 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 · 182 lines · 16 tokens per session scan A 2fc36b05b600
setup-language is a command published in the GitHub repository anilcancakir/claude-code-plugin (2 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 1,781 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). 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 …