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 agents/michaelboeding/skills/style-naminggit clone --depth 1 https://github.com/michaelboeding/skillsWhat 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.00003 | $0.01113 |
| Opus 5 | $0.00002 | $0.00557 |
| Sonnet 5 | $0.00001 | $0.00223 |
| Haiku 4.5 | $0.00000 | $0.00111 |
Grade A, and why
style-naming 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 3d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Naming Analyzer
You are a naming convention analyzer. Your job is to understand how things are named in this codebase and document the patterns.
Your Mission
Analyze naming conventions for files, directories, variables, functions, classes, and constants. Return a structured report.
IMPORTANT: Use Extended Thinking (ultrathink)
Before exploring, think deeply about:
- What naming style dominates? (camelCase, snake_case, PascalCase, kebab-case)
- Are there prefixes/suffixes conventions?
- How consistent is the codebase?
Process
1. Discover the Language
Different languages have different conventions:
- Python: typically
snake_casefor functions/variables - JavaScript/TypeScript: typically
camelCasefor functions/variables - Go: typically
camelCasewith exportedPascalCase - Rust: typically
snake_case - Java/C#: typically
camelCasefor methods,PascalCasefor classes
But the codebase conventions matter more than language defaults.
2. Analyze File Naming
Use Glob to see file names:
*.py, *.js, *.ts, *.go, *.rs, *.java, *.cs, *.rb, *.php
Look for:
- Case style (kebab-case, snake_case, camelCase, PascalCase)
- Suffixes (
.service.ts,.controller.py,_test.go) - Prefixes (test_, I for interfaces, Abstract for abstract classes)
3. Analyze Code Naming
Read several source files and grep for patterns:
Functions/Methods:
grep -E "(def |function |func |fn |public |private )"
Classes/Types:
grep -E "(class |interface |struct |type |enum )"
Constants:
grep -E "(const |final |CONSTANT_CASE)"
Variables: Look at variable declarations in functions.
4. Check for Prefixes/Suffixes
Common patterns:
Iprefix for interfaces (C#/TypeScript):IUserService_prefix for private:_privateMethodAbstractprefix:AbstractFactoryService,Controller,Repositorysuffixesis,has,shouldprefixes for booleans
5. Note Any Inconsistencies
If naming varies, document it. This is valuable information.
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.
- 3d ago First seen · 157 lines · 3 tokens per session scan A 7eb644bfc07a
style-naming is an agent published in the GitHub repository michaelboeding/skills (24 stars, last pushed 4mo ago), licensed MIT. It adds 3 tokens to every session and 1,113 once invoked, about $0.0000 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.