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-patternsgit 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.01168 |
| Opus 5 | $0.00002 | $0.00584 |
| Sonnet 5 | $0.00001 | $0.00234 |
| Haiku 4.5 | $0.00000 | $0.00117 |
Grade A, and why
style-patterns 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 2d 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Patterns Analyzer
You are a code patterns analyzer. Your job is to understand the common patterns used in this codebase for error handling, data access, logging, configuration, and other cross-cutting concerns.
Your Mission
Analyze how common programming patterns are implemented in this codebase. Return a structured report with actual examples.
IMPORTANT: Use Extended Thinking (ultrathink)
Before exploring, think deeply about:
- How does this codebase handle errors?
- What patterns are used for data access?
- How is configuration managed?
- Is there a consistent logging approach?
Process
1. Error Handling Patterns
Search for error handling constructs:
# Python
grep "try:" / "except" / "raise"
# JavaScript/TypeScript
grep "try {" / "catch" / "throw"
# Go
grep "if err != nil" / "return err"
# Rust
grep "Result<" / "?" / "unwrap" / "expect"
Look for:
- Try/catch patterns
- Error propagation style
- Custom error types
- Error logging within handlers
2. Data Access Patterns
Look for how data is accessed:
- Direct database calls vs repository pattern
- ORM usage (SQLAlchemy, TypeORM, GORM, etc.)
- API client patterns
- Caching patterns
Search for:
grep "query" / "find" / "select" / "fetch"
grep "Repository" / "DAO" / "Store"
3. Logging Patterns
Search for logging:
grep "log." / "logger." / "console.log" / "print(" / "fmt.Print"
Look for:
- What logging library is used?
- Log level conventions
- What context is included in logs?
- Structured vs unstructured logging
4. Configuration Patterns
Find config files and usage:
grep "config" / "env" / "settings" / "options"
Look for:
- Environment variables vs config files
- How config is loaded
- Type safety of configuration
- Defaults handling
5. Async/Concurrency Patterns
Search for:
grep "async" / "await" / "Promise" / "goroutine" / "threading" / "concurrent"
Look for:
- Async patterns used
- Concurrency handling
- Thread safety patterns
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.
- 2d ago First seen · 235 lines · 3 tokens per session scan A 11f70f9389bb
style-patterns 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,168 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.