Borrowing it
Nothing to install: this file belongs to agentculture/arxivist. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/agentculture/arxivist/main/.claude/skills/agent-config/SKILL.mdgit clone --depth 1 https://github.com/agentculture/arxivistWrote 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/agentculture/arxivist/agent-config)<a href="https://agentmods.dev/skills/agentculture/arxivist/agent-config"><img src="https://agentmods.dev/badge/skills/agentculture/arxivist/agent-config.svg" alt="Measured on agentmods" 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.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 6d 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.
- 6d ago First seen · 83 lines · 124 tokens per session scan A ef565233ed3e
agent-config is a skill published in the GitHub repository agentculture/arxivist (2 stars, last pushed 1mo ago), licensed MIT. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…