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/managedcode/geminisharpsdk/mcaf-formattingnpx skills add managedcode/GeminiSharpSDK --skill mcaf-formattinggit clone --depth 1 https://github.com/managedcode/GeminiSharpSDKWhat 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.00049 | $0.00325 |
| Opus 5 | $0.00024 | $0.00162 |
| Sonnet 5 | $0.00010 | $0.00065 |
| Haiku 4.5 | $0.00005 | $0.00032 |
Grade A, and why
mcaf-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 yesterday.
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.
What it actually says
MCAF: Formatting
Outputs
- Formatted code changes (consistent with repo style)
- Evidence: formatting command(s) run and any follow-up build/tests
Workflow
- Use the canonical
formatcommand fromAGENTS.md(do not invent commands). - Run the formatter on the smallest scope possible (if your tools allow it).
- Review the diff:
- ensure changes are formatting-only
- if the formatter touched many files, separate the change or confirm it was explicitly requested
- Verify (follow
AGENTS.mdfor sequencing + required commands):- for formatting-only changes: run the smallest meaningful verification the repo requires (build/tests/analyze as applicable)
- for formatting as part of a behaviour change: follow the repo’s normal order (don’t reorder the pipeline)
- If
format/linters are missing or flaky:- fix
AGENTS.mdto point to a real, repeatable command - only then rerun formatting
- fix
- Report what was run and what changed.
Guardrails
- Do not introduce unrelated refactors under the cover of formatting.
- Keep formatting changes and behaviour changes reviewable.
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.
- yesterday First seen · 33 lines · 49 tokens per session scan A aeb5bb72eae1
mcaf-formatting is a skill published in the GitHub repository managedcode/GeminiSharpSDK (2 stars, last pushed 4mo ago), licensed MIT. It adds 49 tokens to every session and 325 once invoked, about $0.0002 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
security-patcher
Invoke this as your absolute first action before using any other tools whenever a user requests to fix, patch, or remediate a vulnerability. Do not perform manual research first.
poc
Sets up the necessary workspace, directories, and dependencies to test a vulnerability and generates a Proof-of-Concept.
dependency-manager
Safely resolve and install isolated dependencies for isolated sandboxes (PoC execution).
architecture
Project architecture and file structure conventions for all process types. Use when: (1) Creating new files or modules, (2) Deciding where code should go, (3) Converting single-file components to directories, (4) Reviewing code for structure compliance, (5) Adding new bridges, services, agents, or workers.
testing
Testing workflow and quality standards for writing and running tests. Use when: (1) Writing new tests, (2) Adding a new feature that needs tests, (3) Modifying logic that has existing tests, (4) Before claiming a task is complete.
widget-creator
Step-by-step guide for creating new widgets in the Hex1b TUI library. Use when implementing new widgets from scratch, including widget records, nodes, extension methods, theming, reconciliation, and tests.