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 agentmods add skills/justinjdev/fellowship/wardennpx skills add justinjdev/fellowship --skill wardengit clone --depth 1 https://github.com/justinjdev/fellowshipWhat 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 | $0.00045 | $0.01007 |
| Opus 5 | $0.00023 | $0.00504 |
| Sonnet 5 | $0.00009 | $0.00201 |
| Haiku 4.5 | $0.00005 | $0.00101 |
Grade A, and why
warden 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 3d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Warden — Catch Convention Violations Before Your Reviewer Does
Overview
Strict review simulation. Compares your code against the project's reference files and documented conventions, flagging every deviation. The goal is to catch the feedback that causes multi-day review rework before you open the PR.
When to Use
- Code is functionally complete and you're about to open a PR
- Any time you've written more than ~50 lines of new code
- Working in an area where past reviews have been painful
Process
Step 1: Gather Context
Read three things:
- Your changes — every file modified or created in this PR
- Reference files — from CLAUDE.md
## Reference Filessection for the relevant area - Conventions — from CLAUDE.md
## Review Conventionssection
If reference files aren't documented, ask:
"I need reference files to compare against. Can you point me to a similar file that your reviewer would approve of?"
If conventions aren't documented, proceed with reference file comparison only and note: "You should run /chronicle to build up your conventions list."
Step 2: Convention Check
For every rule in ## Review Conventions, check compliance:
| # | Convention | Status | Detail |
|---|-----------|--------|--------|
| 1 | [rule text] | PASS/FAIL/N/A | [specific evidence] |
| 2 | ... | ... | ... |
Step 3: Reference Comparison
Compare your code against reference files across every dimension:
Structure
- File organization matches reference
- Import ordering matches reference
- Section ordering matches reference
Patterns
- Dependency access matches reference approach
- Error handling follows same pattern (types, propagation, messaging)
- Data flow follows same layers
- No bypassed abstractions (e.g., direct DB calls when reference uses repository)
Naming
- Variable naming matches reference style
- Function naming matches reference verb patterns
- Type/interface naming matches reference conventions
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.
- 3d ago First seen · 121 lines · 45 tokens per session scan A f1ab30075a65
warden is a skill published in the GitHub repository justinjdev/fellowship (5 stars, last pushed 20d ago), licensed Apache-2.0. It adds 45 tokens to every session and 1,007 once invoked, about $0.0002 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 skills, from other repositories
plan
Use when a request needs shaping before any code is written — a rough or vague prompt to sharpen, an ambiguous idea to design, or a clear-enough task to decompose. One chain-starter that amplifies the prompt, designs the approach, and decomposes it into a batched task file, skipping whichever phases the request…
orbit
Running autonomous loops for nexus-autoloop. Generates script sets from goals, designs operation contracts, audits live loops, and recovers state — runners that complete reliably.
bond
Designing retention strategy, re-engagement, and churn prevention: retention analysis frameworks, re-engagement triggers, gamification, habit formation, and loyalty programs.
clause
Reviewing legal documents for Terms of Service, Privacy Policy, and Tokushoho compliance. Detects clause gaps and flags risks. Not a substitute for legal advice — consult a lawyer.
crest
Building engineer self-branding by turning technical contributions into a professional brand. Use for GitHub/LinkedIn/blog/conference positioning or content strategy.
grok
Designing regex, parsers, and DSLs for grammar authoring and ReDoS-safe regex. Not for REST APIs (Gateway) or DB schemas (Schema).