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 skills add dallay/agents-skills --skill prettier-formattinggit clone --depth 1 https://github.com/dallay/agents-skillsWrote 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/dallay/agents-skills/prettier-formatting)<a href="https://agentmods.dev/skills/dallay/agents-skills/prettier-formatting"><img src="https://agentmods.dev/badge/skills/dallay/agents-skills/prettier-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.1 | $0.00065 | $0.01528 |
| Opus 5 | $0.00032 | $0.00764 |
| Sonnet 5 | $0.00013 | $0.00306 |
| Haiku 4.5 | $0.00006 | $0.00153 |
Grade A, and why
prettier-formatting 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 7d 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
- Setting up Prettier in a new or existing project for consistent formatting.
- Configuring
.prettierrcoptions to match team style preferences. - Integrating Prettier with ESLint without rule conflicts.
- Adding format-on-save in VS Code, JetBrains, or other editors.
- Setting up pre-commit hooks to enforce formatting before code is committed.
- Adding file-type-specific overrides (e.g., different
printWidthfor Markdown vs TypeScript).
Critical Patterns
- Prettier Decides, You Don't Argue: Prettier is intentionally opinionated. Configure only the options it exposes — do NOT fight its AST-based formatting decisions with hacks.
- ESLint Separation: Use
eslint-config-prettierto disable ESLint formatting rules. Do NOT useeslint-plugin-prettier— it's slow and mixes concerns. Run Prettier and ESLint as separate steps. - Ignore Correctly: Always create
.prettierignoreto skip generated files, build output, and lock files. Prettier reads.gitignoreby default, but explicit ignores prevent accidents. - Pin the Version: Lock the Prettier version in
package.jsonto avoid formatting churn across developer machines and CI. - Format All or Nothing: When adding Prettier to an existing project, do one full format commit. Never mix formatting changes with logic changes in the same commit.
- Pre-Commit Enforcement: Use
lint-staged+husky(orlefthook) to format only staged files. Running Prettier on the entire repo per commit is wasteful.
Code Examples
Configuration (.prettierrc.json)
{
"printWidth": 100,
"tabWidth": 2,
"useTabs": false,
"semi": true,
"singleQuote": true,
"trailingComma": "all",
"bracketSpacing": true,
"arrowParens": "always",
"endOfLine": "lf",
"proseWrap": "preserve",
"htmlWhitespaceSensitivity": "css",
"singleAttributePerLine": false
}
File-Type Overrides
{
"printWidth": 100,
"singleQuote": true,
"trailingComma": "all",
"overrides": [
{
"files": "*.md",
"options": {
"printWidth": 80,
"proseWrap": "always"
}
},
{
"files": ["*.json", "*.jsonc"],
"options": {
"tabWidth": 2,
"trailingComma": "none"
}
},
{
"files": "*.yaml",
"options": {
"tabWidth": 2,
"singleQuote": false
}
}
]
}
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.
- 7d ago First seen · 225 lines · 65 tokens per session scan A 8668c7a19307
prettier-formatting is a skill published in the GitHub repository dallay/agents-skills (2 stars, last pushed 15d ago), licensed MIT. It adds 65 tokens to every session and 1,528 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…