agentleFS
Sign inStart free
zedarvateszedarvates/frugal-skills/skills/cardinal/SKILL.md

cardinal

Skill1 starsChanged 32 days agoMITView on GitHub

Instructions for an upstream adversarial review workflow with counter-auditor, counter-developer, counter-optimizer and verdict orchestration. Use to challenge an existing result on critical work. Not for producing the first audit or fixes (mousquetaires), or mechanically reviewing one diff (simplify-code).

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: After Blue Team pipeline, for critical code or health < 70.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 Mousquetaires du Cardinal — Red 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.

Commands, APIs and runtime behavior described below are conditional examples for a compatible upstream installation; they are not evidence of execution in this package.

When NOT to use

  • You need the first pass that produces the work being challenged — use mousquetaires.
  • You need one diff reviewed and simplified — use simplify-code.
  • You need static findings rather than a challenge — use code_* or fallow_like. Adversarial agents that challenge the Blue Team's work.

Trigger: After Blue Team pipeline, for critical code or health < 70.

Agents:

  • 🗡️ Rochefort: Counter-auditor (finds what Porthos missed)
  • 🔪 Milady: Counter-developer (finds what d'Artagnan broke)
  • 🕯️ Comte de Wardes: Counter-optimizer (finds over-optimizations)
  • 👑 Le Cardinal: Orchestrator (coordinates, verdict)

Workflow: rochefort ∥ milady ∥ comte_de_wardes → cardinal

Module: skills/cardinal Upstream pre-prompts: skills/cardinal/prompts/ + skills/core-agent.md; these resources are not bundled in this catalog. Obtain and review a compatible upstream version before attempting the named pipeline.

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.

Check your setup, free