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 skills/jonlwowski012/copilot-agent-factory/code-formattingnpx skills add jonlwowski012/copilot-agent-factory --skill code-formattinggit clone --depth 1 https://github.com/jonlwowski012/copilot-agent-factoryWrote 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/skills/jonlwowski012/copilot-agent-factory/code-formatting)<a href="https://agentmods.dev/skills/jonlwowski012/copilot-agent-factory/code-formatting"><img src="https://agentmods.dev/badge/skills/jonlwowski012/copilot-agent-factory/code-formatting.svg" alt="Measured on agentmods" 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 | $0.00015 | $0.02555 |
| Opus 5 | $0.00008 | $0.01277 |
| Sonnet 5 | $0.00003 | $0.00511 |
| Haiku 4.5 | $0.00002 | $0.00255 |
Grade A, and why
code-formatting 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 4d 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.
wget https://github.com/google/google-java-format/releases/download/v1.17.0/google-java-format-1.17.0-all-deps.jar How it starts
The opening of the file, as written. The whole thing — 457 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Code Formatting
When to Use This Skill
This skill activates when you need to:
- Format code to match project style guidelines
- Fix linting errors
- Set up automatic code formatting
- Understand project formatting standards
Prerequisites
Check project for existing formatting configuration:
.prettierrc,.eslintrc(JavaScript/TypeScript).black,pyproject.toml,ruff.toml(Python).rustfmt.toml(Rust).gofmtsettings (Go)
Step-by-Step Workflow
Step 1: Detect Formatting Tools
Check {{lint_command}} or look for:
package.jsonscripts:"format","lint","lint:fix"- Configuration files in project root
.pre-commit-config.yamlfor pre-commit hooks- CI/CD workflows for formatting checks
Step 2: Format Code by Tech Stack
Python
Option A: Black (Opinionated)
# Install
pip install black
# Format all Python files
black .
# Format specific file
black myfile.py
# Check without modifying
black --check .
# Preview changes
black --diff .
Add to pyproject.toml:
[tool.black]
line-length = 88
target-version = ['py310']
include = '\.pyi?$'
extend-exclude = '''
/(
# directories
\.eggs
| \.git
| \.venv
| build
| dist
)/
'''
Option B: Ruff (Fast, Modern)
# Install
pip install ruff
# Format code
ruff format .
# Check and fix linting
ruff check --fix .
# Check only
ruff check .
Add ruff.toml:
line-length = 88
target-version = "py310"
[lint]
select = ["E", "F", "I", "N", "W"]
ignore = ["E501"]
[format]
quote-style = "double"
indent-style = "space"
Option C: autopep8
# Install
pip install autopep8
# Format file
autopep8 --in-place --aggressive --aggressive myfile.py
# Format all files
find . -name '*.py' -exec autopep8 --in-place --aggressive --aggressive {} \;
JavaScript/TypeScript
Option A: Prettier
# Install
npm install --save-dev prettier
# Format all files
npx prettier --write .
# Format specific files
npx prettier --write "src/**/*.{js,jsx,ts,tsx,json,css,md}"
# Check formatting
npx prettier --check .
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.
- 4d ago First seen · 457 lines · 15 tokens per session scan A c849f5a21bd3
code-formatting is a skill published in the GitHub repository jonlwowski012/copilot-agent-factory (16 stars, last pushed 4mo ago), licensed MIT. It adds 15 tokens to every session and 2,555 once invoked, about $0.0001 per session on Opus 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…