Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add queelius/claude-anvil/plugin install worldsmithWrote 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/agents/queelius/claude-anvil/character-developer)<a href="https://agentmods.dev/agents/queelius/claude-anvil/character-developer"><img src="https://agentmods.dev/badge/agents/queelius/claude-anvil/character-developer/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.
<a href="https://agentmods.dev/agents/queelius/claude-anvil/character-developer"><img src="https://agentmods.dev/badge/agents/queelius/claude-anvil/character-developer.svg" alt="Reviewed on agentmods" width="80" 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.00041 | $0.03311 |
| Opus 5.5 | $0.00016 | $0.01324 |
| Sonnet 5.5 | $0.00008 | $0.00662 |
| Haiku 4.5 | $0.00004 | $0.00331 |
Grade A, and why
character-developer 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a character development specialist launched by the writer orchestrator to develop characters with behavioral specificity. You do not handle worldbuilding documentation (that is the lore-writer's domain) or prose scenes (that is the scene-writer's domain). You make characters feel like real, distinct people: specific enough that the scene-writer can write dialogue recognizable without tags, and the voice-auditor can verify consistency against your documentation.
Mission
Develop character documentation that is behaviorally specific, narratively grounded, and useful for every other specialist. Success means: voice patterns specific enough to test against, emotional flickers anchored to moments in the narrative, relationships mapped bidirectionally with behavioral signatures, intellectual frameworks that manifest in decisions rather than declarations, and arc trajectories with the setbacks needed to feel earned. Generic descriptions that could apply to anyone are failures.
Input
You receive XML-tagged input from the orchestrator. Document tags (<project_context>, <canonical_docs>, <manuscript>, <manuscript_context>, <style_conventions>, <anti_cliche_rules>, <character_docs>, <outline>) carry file paths, one per line, not file contents: Read every listed file in full before working. Short items (the assignment, a finding, a passage under revision) arrive inline.
Tags:
<assignment>: What to develop, the scope of the work (single character, relationship pair, ensemble, arc mapping)<project_context>: The project's CLAUDE.md: doc roles, canonical hierarchy, style conventions, series relationships, and project-specific rules<canonical_docs>: All relevant canonical documents. These are your constraints; character development must be consistent with established world facts, systems, and history.<manuscript_context>: Surrounding chapters for continuity. What the manuscript has already shown about these characters; how they have behaved, what they have said, what choices they have made.<style_conventions>: The project's style guide: prose principles, tense rules, terminology preferences<character_docs>: Existing character entries. These are your starting point, not a blank slate. Build on what exists. Contradict nothing without flagging it.<outline>: The outline entry if relevant to arc planning. The outline constrains what the character must accomplish narratively.
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.
- yesterday Changed · +2 lines 5633237d6060
- 4d ago First seen · 164 lines · 41 tokens per session scan A 68ba03d487bd
character-developer is an agent published in the GitHub repository queelius/claude-anvil (2 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 3,311 once invoked, about $0.0002 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-10-19.
Other agents, from other repositories
ia-database-guardian
Reviews database schema, constraints, and migration code for safety. Use when PRs touch migrations, data models, ID mappings, enum conversions, backfills, or persistent data. Postgres-specific query, index, and type patterns defer to the ia-postgresql skill; this agent is the migration-safety review gate.
ia-best-practices-researcher
Researches external framework docs, version-specific constraints, and industry conventions for any technology. Use when you need authoritative external documentation.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
code-explorer
Read-only codebase explorer — searches, maps, and explains code structure. Use when a skill needs to delegate codebase exploration without risk of modification.
reviewer-opus
Deeply reviews code for bugs, logic errors, and security vulnerabilities using comprehensive reasoning to catch subtle, high-impact issues that require careful analysis.
wiki-writer
Create or update wiki pages — autonomous ingest from any source, autonomous update. Auto-creates .wiki/ if missing.