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 skills add justinjdev/fellowship --skill missivegit clone --depth 1 https://github.com/justinjdev/fellowshipWrote 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/justinjdev/fellowship/missive)<a href="https://agentmods.dev/skills/justinjdev/fellowship/missive"><img src="https://agentmods.dev/badge/skills/justinjdev/fellowship/missive/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/skills/justinjdev/fellowship/missive"><img src="https://agentmods.dev/badge/skills/justinjdev/fellowship/missive.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.00054 | $0.01227 |
| Opus 5.5 | $0.00022 | $0.00491 |
| Sonnet 5.5 | $0.00011 | $0.00245 |
| Haiku 4.5 | $0.00005 | $0.00123 |
Grade A, and why
missive 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Missive — GitHub Issue Context
Overview
Fetches structured context from one or more GitHub issues to inform quest planning. Extracts titles, bodies, labels, comments, and produces branch name suggestions and PR close keywords. Designed for both standalone use (display to user) and as input to Gandalf's quest spawning.
When to Use
- Before spawning a quest from a GitHub issue
- When you need structured issue context for planning
- Invoked with
/missive #42or/missive 42 51 67
Input
Accepts one or more GitHub issue references as arguments:
- Single:
#42or42 - Multiple:
#42 #51 #67or42 51 67 - Mixed:
#42 51 #67
If no arguments are provided, respond with:
"Usage:
/missive <issue>...— provide one or more issue numbers (e.g.,/missive #42or/missive 42 51 67)."
Process
Step 1: Parse Issue Numbers
Extract all issue numbers from the args using the pattern #?\d+. Strip any # prefix to get the raw number.
Step 2: Load Configuration
Read ~/.claude/fellowship.json if it exists. Extract:
branch.pattern— branch name pattern with placeholders (default:null, effective:fellowship/{slug})branch.ticketPattern— regex for ticket extraction (default:[A-Z]+-\d+)issues.autoClose— whether PRs should auto-close issues (default:true)
If the config file doesn't exist, use all defaults.
Step 3: Verify gh CLI
Before fetching, confirm gh is available:
gh --version
If gh is not installed or not authenticated, respond with:
"The
ghCLI is required but not available. Install it from https://cli.github.com/ and authenticate withgh auth login."
Step 4: Fetch Issue Data
For each issue number, run:
gh issue view <number> --json title,body,labels,comments,assignees,milestone
If an issue is not found (non-zero exit), note the error and continue with remaining issues. Do not abort the entire operation for a single missing issue.
Step 5: Build Structured Output
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 Changed · +13 tokens per session d30ae84d2350
- 1mo ago First seen · 130 lines · 41 tokens per session scan A 31facb1d2514
missive is a skill published in the GitHub repository justinjdev/fellowship (5 stars, last pushed 16d ago), licensed Apache-2.0. It adds 54 tokens to every session and 1,227 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-08-31.
Other skills, from other repositories
artifact-metadata
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle.
steward-prep-delivery
Steward-assisted prep for filing issues and PRs — environment capture, template selection, duplicate detection, delivery-policy compliance check.
effect-ledger
Record an effect, sign an effect, reconcile an effect or check "did this PR merge" through the signed AIWG effect ledger, using one aiwg effect command with scriptable exit codes.
contribute-start
Initialize an AIWG contribution workflow by creating a feature branch, configuring DCO, and linking a tracking issue.
launch
Planning releases and reporting delivery work from GitHub PR history. Use when versioning, CHANGELOGs, rollout or rollback plans, engineering metrics, retrospectives, or stakeholder reports are needed.
aiwg-delivery-pr
AIWG-specific delivery pull request workflow; explicit alias for aiwg-pr, not a generic repository PR guide.