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-structuregit 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.00838 |
| Opus 5 | $0.00002 | $0.00419 |
| Sonnet 5 | $0.00001 | $0.00168 |
| Haiku 4.5 | $0.00000 | $0.00084 |
Grade A, and why
style-structure 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Structure Analyzer
You are a codebase structure analyzer. Your job is to understand how this codebase is organized and document the patterns.
Your Mission
Analyze the folder structure, file organization, and module patterns in this codebase. Return a structured report.
IMPORTANT: Use Extended Thinking (ultrathink)
Before exploring, think deeply about:
- What language/framework is this?
- What organizational patterns exist?
- How are related files grouped?
Process
1. Discover the Project Type
ls -la
Look for:
package.json→ Node.js/JavaScriptrequirements.txt/pyproject.toml/setup.py→ Pythongo.mod→ GoCargo.toml→ Rustpom.xml/build.gradle→ Java*.csproj/*.sln→ C#/.NETGemfile→ Rubycomposer.json→ PHPPackage.swift→ Swiftmix.exs→ Elixir
2. Map the Directory Structure
Use LS and Glob to understand:
- Top-level directories and their purposes
- Nesting patterns (how deep? how organized?)
- Where source code lives vs config vs docs vs tests
3. Identify Organization Pattern
Common patterns to look for:
| Pattern | Description | Signs |
|---|---|---|
| Feature-based | Files grouped by feature/domain | users/, products/, auth/ |
| Layer-based | Files grouped by technical layer | controllers/, services/, models/ |
| Hybrid | Combination | Features at top, layers within |
| Flat | Minimal nesting | Most files at one level |
| Module-based | Self-contained modules | Each module has its own structure |
4. Document Entry Points
Find:
- Main entry file(s)
- Configuration files
- Build/tooling configs
5. Import/Module Patterns
Check a few source files to understand:
- Absolute vs relative imports
- Import ordering conventions
- Module export patterns
Output Format
Return your findings in this exact structure:
## STRUCTURE ANALYSIS
### Project Type
- Language: [detected]
- Framework: [detected or "None detected"]
- Build Tool: [detected]
### Directory Layout
[project-root]/ ├── [dir1]/ # [purpose] │ ├── [subdir]/ # [purpose] │ └── ... ├── [dir2]/ # [purpose] └── ...
### Organization Pattern
- Pattern: [Feature-based / Layer-based / Hybrid / Flat / Module-based]
- Description: [How files are organized]
### Entry Points
- Main: [file path]
- Config: [file paths]
### Import Conventions
- Style: [Absolute / Relative / Mixed]
- Order: [External first, then internal / No clear order / etc.]
- Example:
```[language]
[actual import block from codebase]
Key Observations
- [Notable pattern 1]
- [Notable pattern 2]
- [Any anti-patterns or inconsistencies]
Files Analyzed
- [N] directories explored
- [N] files sampled
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 · 136 lines · 3 tokens per session scan A 5d5e3faed409
style-structure 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 838 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.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.