Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add itsribbZ/Godspeed/plugin install godspeedWrote 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/itsribbz/godspeed/holy-trinity)<a href="https://agentmods.dev/skills/itsribbz/godspeed/holy-trinity"><img src="https://agentmods.dev/badge/skills/itsribbz/godspeed/holy-trinity.svg" alt="Measured on agentmods" 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.00058 | $0.09045 |
| Opus 5 | $0.00029 | $0.04522 |
| Sonnet 5 | $0.00012 | $0.01809 |
| Haiku 4.5 | $0.00006 | $0.00904 |
Grade A, and why
holy-trinity 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 5d 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 — 745 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Holy Trinity v4.0 — Adaptive Convergent Improvement Engine
When to Trigger
- User says "holy trinity", "deploy holy trinity", "run holy trinity", "trinity on [topic]"
- User says "upgrade [system]", "self-improve [system]", "make [system] better"
- User wants the complete diagnose → research → implement → verify loop
- When a system, skill, or architecture needs measured improvement, not just research
Target Type Auto-Presets (v2.0)
Before scoring, auto-detect the target type and load preset scoring dimensions. This eliminates the manual dimension-definition step from v1.0.
Preset Library (validated across 5+ runs)
| Target Type | Detection Signal | Dimensions (7 × 0-5 = 35 max) |
|---|---|---|
| Code/Architecture | Source files, .h/.cpp, .ts/.tsx | Law1:Simplicity, Law2:DataDriven, Law3:EdgeCases, Law4:Decoupling, Law5:Liability, Law6:Disclosure, Law7:WorkRightFast |
| Skill/Tool | SKILL.md, _learnings.md, .claude/skills/ | Reliability, SelfImprovement, CrossSkillIntegration, Resilience, OutputQuality, Efficiency, Extensibility |
| Game Design | GDD, design docs, no code target | Coherence, ScopeFeasibility, CoreLoop, Differentiation, Interconnection, TechSpec, PlayerMotivation |
| Product/Business | Market analysis, revenue model | MktValidation, CompetitiveGap, RevenueModel, BuildFeasibility, DistributionPath, UniqueAdvantage, ScalePotential |
| Standalone Tool | Python/script, standalone app | FeatureCompleteness, Architecture, SafetyReliability, UX, Extensibility, Documentation, Integration |
| Infrastructure | CI/CD, deploy, configs | Reliability, Security, Observability, Automation, Recovery, Scalability, Maintainability |
| Custom | Cannot auto-detect | Define 7 dimensions in Phase 0 — document rationale |
Cross-run note: When running on a target that matches a previous run's type, load that run's scoring calibration notes. If the previous run flagged "dimension X was most impactful", weight it higher.
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.
- 5d ago First seen · 745 lines · 58 tokens per session scan A 0b0f9c77cd8b
holy-trinity is a skill published in the GitHub repository itsribbZ/Godspeed (1 stars, last pushed 2mo ago), licensed MIT. It adds 58 tokens to every session and 9,045 once invoked, about $0.0003 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
release-it
Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or…
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
git-investigate
Git history investigation. Use when: tracking code changes, finding where bugs were introduced, root cause analysis. Not for: code exploration (use code-explore), issue analysis (use issue-analyze). Output: history trace + root cause report.
analyze
Deep-dive codebase analysis that explains how things actually work — business rules, architecture patterns, auth flows, data models, integrations, and performance hotspots. Use whenever the user asks "how does X work", "map the Y flow", "what are the business rules for Z", "trace the auth path", "explore the codebase…
simplify
Wrap-up refactoring — simplify code, eliminate duplication, preserve behavior.
incremental-analysis
Detect existing workspace, diff current sources against high water mark metadata, classify specs as unchanged/stale/orphaned/new, re-analyze only what changed. Activates automatically when /analyze finds an existing workspace.