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 fakoli/fakoli-plugins --skill style-opsgit clone --depth 1 https://github.com/fakoli/fakoli-pluginsWrote 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/fakoli/fakoli-plugins/style-ops)<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/style-ops"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/style-ops/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/style-ops"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/style-ops.svg" alt="Reviewed on agentmods" width="80" 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.00026 | $0.00430 |
| Opus 5.5 | $0.00010 | $0.00172 |
| Sonnet 5.5 | $0.00005 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
style-ops 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 1mo 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.
What it actually says
Style operations
Resolve the plugin root from this skill's location. Its bundled data/principles.json and generated report are readable reference data. For changes, select the user's durable source checkout or explicit ledger/output files; do not silently edit an installed cache.
-
Read the ledger and schema. For a new principle, use
aspirationalplus concreteopen_work. Preserve existing IDs and history. -
To assert or prove a principle, add repo-relative proof and embodiment pointers. A
provenpointer must refer to a test file and real nested Python symbols when::symbols are present. A valid pointer does not establish that a test passed: run the relevant test and record its result before claiming verification. -
Generate with the packaged script and explicit destinations when working outside the source checkout:
uv run --script "$PLUGIN_ROOT/scripts/generate.py" --data "$LEDGER" --output "$REPORT" uv run --script "$PLUGIN_ROOT/scripts/validate.py" --repo-root "$SOURCE_CHECKOUT" --data "$LEDGER" --doc "$REPORT"Resolve these variables to actual paths.
--repo-rootis the checkout containing the evidence paths; it need not be the plugin install directory.--schemacan select a corresponding custom schema. The generator's--checkmode does not write. -
For reports, summarize proven/asserted/aspirational status and the highest-risk open work. Separate pointer validation, tests actually run, and unverified claims.
When maintaining this marketplace's bundled ledger from its source checkout, the scripts' default data/schema/doc paths apply. Validation resolves a source checkout, never assumes that an arbitrary install cache's grandparents contain the evidence.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · -52 lines a48aa5555381
- 1mo ago First seen · 78 lines · 26 tokens per session scan A d1d272888fc2
style-ops is a skill published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 23d ago), licensed MIT. It adds 26 tokens to every session and 430 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
audit
Read-only quality gate that audits already-built work against its stated requirement and Definition of Done before it is allowed to move to 2done/. Produces a severity-ranked decision proposal (BLOCKER/MAJOR/MINOR/NIT) with evidence; the judgement never edits, only a recorded post-audit step may fix small findings.…
pr-vetting
Use when the user wants to thoroughly investigate, vet, review, or security-scan a pull request before deciding how to handle it - especially PRs from external or unknown contributors. Runs a parallel multi-agent investigation (technical, security, value/fit, contributor reputation) and merges the findings into one…
issue-triage
Use when the user wants to triage GitHub issues - decide whether an issue is still relevant, reproducible, closeable, a duplicate, or what concretely needs doing. Selects and prioritizes first (never dumps all issues at once), then deep-triages the chosen issues via parallel subagents, recommends actions for the owner…
requirements-verbatim
Capture a user requirement, decision, approval, or constraint word-for-word into an append-only dated log so it survives context compaction and can never be trimmed, softened, or reinterpreted. Use whenever the user states or approves a requirement, gives a GO, sets a constraint, or makes any decision that later work…
diag
Read-only root-cause diagnosis for a symptom, bug, failure, or unexpected behavior. Establishes the mechanism at file:line and reads up the facts instead of guessing, before any fix is attempted. Produces a diagnosis report; the fix is always a separate step gated by an explicit GO. Use when something is broken…
sandbox
Do WRITING pre-work for a clarify item that is blocked by a knowledge gap - a missing measurement, a mockup, or a feasibility proof - WITHOUT touching production code, without git, and without disturbing the task / build agent. Use when a 1clarify item cannot be answered by a product decision alone but needs something…