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 ArtemioPadilla/agent-triforce --skill implement-featuregit 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/skills/artemiopadilla/agent-triforce/implement-feature)<a href="https://agentmods.dev/skills/artemiopadilla/agent-triforce/implement-feature"><img src="https://agentmods.dev/badge/skills/artemiopadilla/agent-triforce/implement-feature/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/artemiopadilla/agent-triforce/implement-feature"><img src="https://agentmods.dev/badge/skills/artemiopadilla/agent-triforce/implement-feature.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.00035 | $0.00475 |
| Opus 5.5 | $0.00014 | $0.00190 |
| Sonnet 5.5 | $0.00007 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
implement-feature 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.
What it actually says
Implement the feature: $ARGUMENTS
Follow these steps:
SIGN IN:
- Run the SIGN IN checklist from your agent file
- Run the Receiving-from-Prometeo checklist to verify the spec handoff
- If significant architecture decisions are needed, create an ADR in
docs/adr/
DESIGN:
- Define interfaces/contracts first — program to interfaces, not implementations
- Plan the layer structure: entities → use cases → adapters → frameworks (Clean Architecture)
- Identify which business logic needs TDD (test-first) vs infrastructure glue (test-after acceptable)
BUILD (TDD Cycle): 4. For each piece of business logic: a. Red: Write a failing test that describes the expected behavior (Arrange-Act-Assert) b. Green: Write minimal code to make the test pass c. Refactor: Clean up — extract methods, improve names, remove duplication d. Verify each acceptance criterion from the spec has at least one test — if not, write one before proceeding 5. Implement infrastructure/adapters and write integration tests for critical paths 6. Scan for and remove any dead code you introduced or found
⏸️ TIME OUT — Run Implementation Complete Checklist (DO-CONFIRM): 7. Run through every item in the Implementation Complete checklist from your agent file 8. Fix any failures BEFORE proceeding
REFACTORING PASS: 9. Review all new code for code smells: long methods, feature envy, data clumps, primitive obsession 10. Apply Extract Method, Rename, Move as needed — leave code better than you found it
⏸️ TIME OUT — Run Pre-Delivery Checklist (DO-CONFIRM): 11. Run through every item in the Pre-Delivery checklist from your agent file 12. Fix any failures BEFORE proceeding
SIGN OUT: 13. Write the Handoff-to-Centinela using the communication checklist 14. Run the SIGN OUT checklist from your agent file
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 · 48 lines · 35 tokens per session scan A 5144b57c6f82
implement-feature is a skill published in the GitHub repository ArtemioPadilla/agent-triforce (3 stars, last pushed 6mo ago), licensed MIT. It adds 35 tokens to every session and 475 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-08-31.
Other skills, from other repositories
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
anti-patterns
Catalogue of known SDLC anti-patterns that greatcto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
cost-model
Standardized cost-estimation framework for greatcto plans. Forces explicit LLM cost, infra cost, human-supervision time, and the (defensible) human-equivalent comparison. Output format is parsable by the board's /api/cost path — must follow exactly.
deploy-landed
A deployment verification procedure that checks whether the intended code revision is actually running, its environment settings are present, and the product works. A deployment is the process of putting new software on a server or hosting platform.
stack-baseline
The pinned default technology stack for SMB Product-Builder products. One source of truth so the architect, app-scaffolder, auth-engineer, and senior-dev never re-decide the stack per build — they build ON it. Covers framework, ORM/DB, auth, UI, payments/email/SMS, files, jobs, testing, hosting, and observability…
pm
Project manager for GitHub issues: brainstorm design approaches, create structured issues optimized for LLM agent teams, triage and recommend what to work on next, audit and clean up stale issues, or deep-validate a single issue against the codebase. Triggers: create issue, plan work, new task, project manager, write…