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/ArtemioPadilla/agent-triforceWrote 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/artemiopadilla/agent-triforce/growth-check)<a href="https://agentmods.dev/commands/artemiopadilla/agent-triforce/growth-check"><img src="https://agentmods.dev/badge/commands/artemiopadilla/agent-triforce/growth-check/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/artemiopadilla/agent-triforce/growth-check"><img src="https://agentmods.dev/badge/commands/artemiopadilla/agent-triforce/growth-check.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.00014 | $0.00474 |
| Opus 5 | $0.00007 | $0.00237 |
| Sonnet 5 | $0.00003 | $0.00095 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
growth-check 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 11d 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.
What it actually says
Display the current Agent Triforce growth status. This command is read-only -- it never modifies state.
Run the growth tracker tool and present results from all three subcommands.
1. Current Growth Phase
Run python3 tools/growth-tracker.py status and display:
- Current Phase: Pre-Launch, Soft Launch, Content Momentum, or Community
- Stars: Current GitHub star count from growth log
- Forks: Current fork count
- Repo Age: Days since repository creation
2. Pre-Launch Readiness Gates
Run python3 tools/growth-tracker.py check and display:
- Overall Status: PASS or FAIL
- Gate Results: Each gate with pass/fail status and detail message
- If any gate fails, highlight it prominently with the specific failure reason
The gates checked are:
- README exists
- README methodology keywords above the fold (first 200 words)
- CHANGELOG current and complete
- Growth log baseline entry exists
3. Milestone Actions
Run python3 tools/growth-tracker.py milestones and display:
- Unlocked Actions: Milestones already reached, with the next action to take
- Locked Milestones: What's still needed (stars, repo age) to unlock each action
Milestones from the growth plan (Appendix E):
- Pre-launch readiness (always unlocked)
- Repo 30 days + 10 stars: hesreallyhim resubmission
- 50 stars: Show HN submission
- 100 stars: Demo video production
- 200 stars: hesreallyhim second attempt
- 300 stars: Product Hunt preparation
- 500 stars: GitHub Discussions launch
4. Weekly Logging Reminder
If the most recent growth log entry is more than 7 days old, display a reminder:
"Growth log is stale. Record this week's metrics with:
python3 tools/growth-tracker.py log --stars <count> --forks <count> --visitors <count> --clones <count>"
Format the output clearly with section headers. Use plain text formatting suitable for terminal display.
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.
- 11d ago First seen · 56 lines · 14 tokens per session scan A b00d7c8c19b3
growth-check is a command published in the GitHub repository ArtemioPadilla/agent-triforce (3 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 474 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
rekindle
Recover a fellowship after a session crash. Scans worktrees and quest state, presents a recovery dashboard, and re-spawns Gandalf with recovered quest context. Use when returning to a crashed or expired fellowship session.
settings
View or edit fellowship configuration (/.claude/fellowship.json). Run /settings to see current settings, change values, or reset to defaults.
validate-docs
Validate that site and README documentation is current. Report-only — flags issues without modifying anything.
chronicle
One-time codebase onboarding — interactively extracts your team's conventions, identifies reference files, and generates CLAUDE.md sections so Claude codes the way your team does. Run once per project.
guide
Interactive guide to fellowship. Walks you through a real task using the structured research-plan-implement flow, then shows you what's next.
red-book
Use after receiving PR review feedback. Extracts conventions from reviewer comments and offers to add them to CLAUDE.md. Closes the convention learning loop.