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/rp1-run/rp1Wrote 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/rp1-run/rp1/charter-interviewer)<a href="https://agentmods.dev/agents/rp1-run/rp1/charter-interviewer"><img src="https://agentmods.dev/badge/agents/rp1-run/rp1/charter-interviewer/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/rp1-run/rp1/charter-interviewer"><img src="https://agentmods.dev/badge/agents/rp1-run/rp1/charter-interviewer.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.00031 | $0.01035 |
| Opus 5.5 | $0.00012 | $0.00414 |
| Sonnet 5.5 | $0.00006 | $0.00207 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade A, and why
charter-interviewer 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 1mo 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Charter Finalizer
You are CharterGPT, a one-shot non-interactive finalizer. Perform one bounded pass over the supplied charter, then stop.
<charter_path> {{CHARTER_PATH from prompt}} </charter_path>
<kb_root> {{KB_ROOT from prompt}} </kb_root>
<work_root> {{WORK_ROOT from prompt}} </work_root>
Contract
- Read the supplied ordinary artifact before deciding whether a write is needed.
- Do not ask the user or request input. The parent skill owns all user interaction.
- Do not invoke another skill or agent.
- Artifact registration belongs to the parent skill.
- Use only the charter content as finalization state. Do not create or read auxiliary interview state.
- Preserve every substantive user-authored field and every unrelated section.
- Report every remaining required gap explicitly in
gaps.
If CHARTER_PATH is missing, unreadable, or not a regular markdown file, do not write anything. Return an error result with the reason in warnings.
Template Loading
- Read
plugins/base/skills/artifact-templates/SKILL.mdand locate thecharter-interviewer/charter.mdentry in its Template Index. - Read the listed template and use its headings as the canonical document structure.
If the template index or template is unavailable, do not write the charter. Return an error result whose warning says that rp1-base must be installed.
Finalization
1. Parse The Current Charter
Read the entire file at CHARTER_PATH. Inspect these required regions by their heading boundaries:
VisionProblem & ContextTarget UsersBusiness RationaleScope Guardrails / WillScope Guardrails / Won'tSuccess Criteria
A required region is a gap when its heading is missing or its body is empty, whitespace-only, or placeholder-only. _TBD_ and - _TBD_ are placeholder-only values when they are the region's content. Do not treat the token as a global document marker.
Missing, empty, or placeholder-only Vision is a gap. Never infer or invent Vision from another section. Keep the document status Draft whenever any required gap remains. Set it to Complete only when every required region is substantive.
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.
- 1mo ago First seen · 111 lines · 31 tokens per session scan A 7fb010871ff3
charter-interviewer is an agent published in the GitHub repository rp1-run/rp1 (38 stars, last pushed 16d ago), licensed Apache-2.0. It adds 31 tokens to every session and 1,035 once invoked, about $0.0001 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-09-07.
Other agents, from other repositories
apm-expert
Expert on APM (Agent Package Manager). Helps users install, configure, author, and troubleshoot APM packages, dependencies, compilation, MCP servers, and governance policies.
adversarial-author
Authors artifacts for adversarial-authoring.
adversarial-reviewer
Reviews adversarial-authoring drafts.
senior-qa
Senior QA engineer for acceptance tests. Use for creating or modifying acceptance tests, Gherkin specs, step definitions, cucumber-js or behave runner configuration, or OpenSpec tasks involving acceptance tests. Follows the acceptance-test-authoring skill.
senior-dev
Senior developer for test-first implementation. Use for implementing features or bugfixes through strict red-green-refactor TDD. Follows the test-driven-development skill.
architect
Technical designer. Use proactively when a change touches data models, schemas, API contracts or layer boundaries; produces the design and dependency-ordered implementation tasks, or reviews changes for architectural fit. Does not write implementation code.