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.
git clone --depth 1 https://github.com/reluctantfuturist/loyal-wingmanWrote 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/commands/reluctantfuturist/loyal-wingman/character-map)<a href="https://agentmods.dev/commands/reluctantfuturist/loyal-wingman/character-map"><img src="https://agentmods.dev/badge/commands/reluctantfuturist/loyal-wingman/character-map/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/commands/reluctantfuturist/loyal-wingman/character-map"><img src="https://agentmods.dev/badge/commands/reluctantfuturist/loyal-wingman/character-map.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.00021 | $0.00773 |
| Opus 5 | $0.00010 | $0.00387 |
| Sonnet 5 | $0.00004 | $0.00155 |
| Haiku 4.5 | $0.00002 | $0.00077 |
Grade A, and why
character-map 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/character-map
Display character appearances, relationships, and identify orphaned characters.
Usage
/character-map # Default project (first found)
/character-map [ProjectName] # Specific project
/character-map --orphans # Focus on orphan detection
Process
Step 1: Query Project Context
REQUIRED SUB-SKILL: Invoke query-context with:
- Target: All scene files in
10_Projects/[Project]/Scenes/ - Focus: Extract character references from frontmatter and prose
Query-context will search:
- Scene frontmatter for
pov_character,related_characters 02_World/Characters/for all character entries- Character relationship sections
Step 2: Build Character Map
From query-context results:
## [Project Name] - Character Map
### POV Characters
- **[Character Name]** - Ch 1, 2, 3 (POV all)
### Major Characters (3+ appearances)
- **[Character Name]** - Ch 1, 2, 3
- Relationship: [relationship to protagonist]
- **[Character Name]** - Ch 1, 3
- Relationship: [relationship type]
### Supporting Characters (1-2 appearances)
- **[Name]** - Ch [X]
- Role: [brief description]
### Mentioned Only
- **[Name]** - Referenced in Ch [X]
Step 3: Map Relationships
From character files' relationship sections:
### Relationship Web
[Protagonist]
├── [Character A] (relationship type)
├── [Character B] (relationship type)
└── [Character C] (relationship type)
Key Dynamics:
- [Character 1] ↔ [Character 2]: [dynamic description]
- [Character 1] ↔ [Character 3]: [dynamic description]
Step 4: Validate Links
REQUIRED SUB-SKILL: Invoke validate-links to check:
- All character wikilinks in scenes resolve
- Character files link back to scenes they appear in
- Bidirectional linking between related characters
Step 5: Identify Issues
### Potential Issues
**Missing World Bible Entry:**
- ⚠️ [Name] appears in Ch [X] but no entry in 02_World/Characters/
→ Use world-bible skill to create
**Orphaned Characters:**
- ⚠️ [Name] has world bible entry but doesn't appear in this project
**Link Issues:** (from validate-links)
- ⚠️ [issues reported by validate-links]
**Faction Mentions Without Detail:**
- ⚠️ [Faction] mentioned in Ch [X], no entry in 02_World/Factions/
→ Use world-bible skill to create
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.
- 9d ago First seen · 125 lines · 21 tokens per session scan A b1e6c8b369c4
character-map is a command published in the GitHub repository reluctantfuturist/loyal-wingman (7 stars, last pushed 8mo ago), licensed MIT. It adds 21 tokens to every session and 773 once invoked, about $0.0001 per session on Opus 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.