foolery: Skill for Claude Code

.claude/skills/foolery-configure/SKILL.md

foolery-configure is a skill for Claude Code from acartine/foolery. It costs 95 tokens per session (1,838 once invoked), scanned A, original, MIT.

A setup workflow for Foolery, an agent-management tool. It creates and checks configuration files that describe available coding agents and the repositories Foolery can use.

In plain words
What is it for?
Use it to set up Foolery, add or remove agents, change agent groups, or connect repositories for use by the agents.
Why use it?
It avoids guessing configuration fields and catches invalid settings before Foolery uses them.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions Codex; mentions OpenCode.

This is acartine/foolery's own configuration. It tells Claude Code how to work on foolery itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything foolery configures →

Reuse

Borrowing it

Nothing to install: this file belongs to acartine/foolery. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/acartine/foolery/main/.claude/skills/foolery-configure/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/acartine/foolery

Made for: Claude Code.

Wrote 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.

agentmods badge for foolery-configure

README.md
[![agentmods](https://agentmods.dev/badge/skills/acartine/foolery/foolery-configure/github.svg)](https://agentmods.dev/skills/acartine/foolery/foolery-configure)
Your own site
<a href="https://agentmods.dev/skills/acartine/foolery/foolery-configure"><img src="https://agentmods.dev/badge/skills/acartine/foolery/foolery-configure/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.

agentmods 80×15 button for foolery-configure

Your own site · 80×15
<a href="https://agentmods.dev/skills/acartine/foolery/foolery-configure"><img src="https://agentmods.dev/badge/skills/acartine/foolery/foolery-configure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 95 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,838 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00095 $0.01838
Opus 5.5 $0.00038 $0.00735
Sonnet 5.5 $0.00019 $0.00368
Haiku 4.5 $0.00010 $0.00184

Measured 2mo ago against content hash deefd90d3c8a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

foolery-configure 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 2mo 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.

.claude/skills/foolery-configure/SKILL.md · 171 lines

How it starts

The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/foolery-configure

Produce a valid ~/.config/foolery/settings.toml and ~/.config/foolery/registry.json by inspecting the host, asking the user at most four questions, and validating the result against the shipped schema.

Contract

The authoritative spec for settings.toml is the foolery config CLI:

  • foolery config schema — prints JSON Schema (Draft 2020-12) of the file.
  • foolery config validate [path] — exits 0 with OK <path>, 1 with a field-path breakdown on schema violation, 2 on file/TOML error.

Treat those two commands as the contract. Never guess field names or defaults — read them from foolery config schema.

Inputs to load before asking anything

Run these in the shell and read their output:

  1. cat ~/.config/foolery/settings.toml — existing settings (may not exist).
  2. cat ~/.config/foolery/registry.json — existing mounted repos (may not exist).
  3. foolery config schema — current schema.
  4. For each of claude, codex, opencode, gemini, copilot: run command -v <name> to see whether the CLI is on PATH. For each that resolves, probe for its available models (e.g. claude --help, codex --help, opencode models, gemini models, copilot --list-models). If a probe is unclear, ask the user which models they want — do not assume.

The only four questions you may ask

Ask no more than these, in this order. Skip any whose answer is already unambiguous from existing files or from a single detected CLI.

  1. Which agent vendors? — from the detected subset of claude, codex, opencode, gemini, copilot.
  2. Which models per vendor? — one or more per selected vendor, using the probed model list.
  3. Dispatch mode? — basic (one agent per action) or advanced (weighted pools per workflow step).
  4. Which repos to mount? — absolute paths to add under registry.json.

If a required value cannot be answered, stop and ask the user. Never pick a default to paper over a missing answer — follow the "fail loudly, never silently" rule.

Read the full file on GitHub · 171 lines

Changes

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.

  1. 2mo ago First seen · 171 lines · 95 tokens per session scan A deefd90d3c8a

Subscribe to this mod's changes

foolery-configure is a skill published in the GitHub repository acartine/foolery (60 stars, last pushed 13d ago), licensed MIT. It adds 95 tokens to every session and 1,838 once invoked, about $0.0004 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-08-30.

Related

foolery-configure compared with skills from other repositories

foolery-configure next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
foolery-configureacartine/foolerySkill6013d agoMITA95Claude Code
lavra-ceo-reviewroberto-mello/lavraSkill5315d agoMITA27Claude Code
lavra-reviewroberto-mello/lavraSkill5315d agoMITA15Claude Code
dspy-rubyroberto-mello/lavraSkill5315d agoMITA35Claude Code
lavra-brainstormroberto-mello/lavraSkill5315d agoMITA15Claude Code
lavra-eng-reviewroberto-mello/lavraSkill5315d agoMITA19Claude Code
write-documentationDollarDill/beads-superpowersSkill326d agoMITA56Claude Code