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/agentculture/fleet-cli/agent-confignpx skills add agentculture/fleet-cli --skill agent-configgit clone --depth 1 https://github.com/agentculture/fleet-cliWhat 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.00124 | $0.00987 |
| Opus 5 | $0.00062 | $0.00494 |
| Sonnet 5 | $0.00025 | $0.00197 |
| Haiku 4.5 | $0.00012 | $0.00099 |
Grade A, and why
agent-config 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 2d 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.
This is a copy
100% identical to agent-config — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agent-config — surface a Culture agent's config in one view
guildmaster is the mesh's skills supplier and owns the inventory surfaces: "what kit + config does this agent have?" This skill answers exactly that for a single agent, showing the three artifacts that together define it:
- System-prompt file (
CLAUDE.md/AGENTS.md/GEMINI.md) — the prompt-side guidance for the agent's backend. The script detects which file is present from a backend-fingerprint registry. culture.yaml— the runtime-side config (agents:list withsuffix,backend,model,system_prompt,channels,tags,acp_command,extras). Lives parallel to the prompt file at the project root..claude/skills/*/SKILL.md— the per-project skills the agent can invoke, one line each (name + truncated description).
This is the inventory half of the steward → guildmaster split
(issue #12): it reports
the config, it does not interpret drift or judge alignment. The relationship
graph and the "is this agent aligned?" judgment stay with steward overview /
steward doctor.
When to use
- Before
guild teach/guild onboard— see an agent's current kit + config. - When an operator asks "show me agent
<name>" or "what does<agent>run". - Read it, don't guess — before answering a question about what an agent does.
How to run
One script, two ways to call it (or just run guild show, which wraps it):
# Path mode — point at any directory with a prompt file + culture.yaml
.claude/skills/agent-config/scripts/show.sh ../culture
# Suffix mode — resolve a registered agent suffix via the Culture server's
# manifest (location set by culture_server_yaml in skills.local.yaml)
.claude/skills/agent-config/scripts/show.sh daria
Output is three sections: the detected system-prompt file, culture.yaml (or
(missing)), and a one-line summary per local skill (name + description,
truncated to 120 chars).
What ships with it
2 files 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.
- 2d ago First seen · 83 lines · 124 tokens per session scan A ef565233ed3e
agent-config is a skill published in the GitHub repository agentculture/fleet-cli (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 124 tokens to every session and 987 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to agent-config, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
trulens-notebook-execution
Execute and display Jupyter notebooks for TruLens demos and quickstarts.
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
master-yinguang
Use when user asks about 印光大师, 净土, 念佛, 持名念佛, 十念法, 摄耳谛听, 老实念佛, 信愿行, 带业往生, 仗佛慈力, 自力他力, 竖出横超, 往生, 极乐, 阿弥陀佛, 净土三经, 敦伦尽分, 闲邪存诚, 因果报应, 文钞, 一函遍复, or wants teaching in 印光大师 Yinguang's voice. Triggers include "印光"、"文钞"、"老实念佛"、"信愿行"、"带业往生"、"仗佛慈力"、"横超竖出"、"都摄六根"、"净念相继"、"敦伦尽分"、"闲邪存诚"、"因果"、"十念法"、"摄耳谛听"、"一函遍复"、"净土三经"、"往生" — invoke…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
obsidian-to-clew-import
Convert an Obsidian vault or wiki-linked markdown graph into a validated structured-learning graph package for Clew. Use when the user wants to inspect a vault, preview whether it imports cleanly, preserve explicit relation markers, choose only the few import settings that matter, and produce a fail-closed package…