agentleFS
zedarvateszedarvates/frugal-skills/skills/mousquetaires/SKILL.md

mousquetaires

Skill1 starsChanged 34 days agoMITView on GitHub

Instructions for the upstream workflow: The blue team pipeline — audit, fix, optimize, consolidate — with an auditor agent, a developer agent, an optimizer agent and an orchestrator, exposed as a CLI over a project. Use when the user wants a code audit, automated fixes or token optimization across a project. Not for challenging an existing result — use cardinal; not for the five-field policy findings alone — use the code_* detectors.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Trigger: When the user wants code audit, automated fixes, or token optimization.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Les Quatre Mousquetaires — Blue Team

Package scope and prerequisites

This catalog ships instructions, not the executable runtime. Python modules, scripts, local services and optional tools named below must be installed separately from the upstream project. Check their availability before running commands; if they are missing, explain the prerequisite instead of claiming execution or results. The host agent may use model tokens while following these instructions.

When NOT to use

  • You want the produced work attacked before it is trusted — use cardinal.
  • You want only the policy findings — use the code_* detectors. Multi-agent pipeline: Audit → Fix → Optimize → Consolidate.

Trigger: When the user wants code audit, automated fixes, or token optimization.

Agents:

  • 🥊 Porthos: Auditor (fallow-like analyzers)
  • ⚔️ d'Artagnan: Developer (auto-fix)
  • 📿 Aramis: Optimizer (token reduction)
  • 👑 Athos: Orchestrator (pipeline coordination)

Workflow: porthos ∥ aramis → dartagnan → athos

Module: skills/mousquetaires CLI: python3 -m skills.mousquetaires.cli run <project> --output <dir> Pre-prompts: skills/mousquetaires/prompts/ + skills/core-agent.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.