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 feature-specgit 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/feature-spec)<a href="https://agentmods.dev/skills/artemiopadilla/agent-triforce/feature-spec"><img src="https://agentmods.dev/badge/skills/artemiopadilla/agent-triforce/feature-spec/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/feature-spec"><img src="https://agentmods.dev/badge/skills/artemiopadilla/agent-triforce/feature-spec.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.00033 | $0.00510 |
| Opus 5.5 | $0.00013 | $0.00204 |
| Sonnet 5.5 | $0.00007 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
feature-spec 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
Create a feature specification for: $ARGUMENTS
Follow these steps:
SIGN IN:
- Run the SIGN IN checklist from your agent file
- Surface any initial concerns about this feature request
TIER SELECTION:
- Ask the user which spec tier to use:
- S (Small): Bug fix, tweak, minor enhancement (~10 min)
- M (Medium): Standard feature — default choice (~30-60 min)
- L (Large): Epic, multi-phase, API-heavy (~60-90 min)
- If the user does not specify, default to M
RESEARCH (READ-DO):
3. Read existing specs in docs/specs/ to understand current patterns and avoid conflicts
4. Identify dependencies on existing features or systems
BUILD:
5. Create the spec at docs/specs/{feature-name}.md using the tier-appropriate template from your system prompt
6. For each user story, validate against INVEST:
- Independent: can be delivered separately
- Negotiable: not a rigid contract, allows discussion
- Valuable: delivers value to user or business
- Estimable: Dev can estimate effort
- Small: fits in one iteration
- Testable: has clear acceptance criteria
- For M/L tiers, verify IEEE 830 quality attributes: completeness, consistency, unambiguity, verifiability
- For M/L tiers, fill in testing considerations: identify the 2-3 highest-risk acceptance criteria, recommend a test design technique for each (BVA for bounded inputs, EP for categorical inputs, Decision Table for complex branching, State Transition for lifecycle objects), note test data needs, and flag non-functional test requirements
TIME OUT -- Run Spec Completion Checklist (DO-CONFIRM): 8. Run through every item in the Spec Completion checklist from your agent file 9. Fix any gaps BEFORE proceeding
SIGN OUT: 10. Write the Handoff-to-Forja using the communication checklist 11. 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 · 33 tokens per session scan A f8c0eeb94f31
feature-spec is a skill published in the GitHub repository ArtemioPadilla/agent-triforce (3 stars, last pushed 6mo ago), licensed MIT. It adds 33 tokens to every session and 510 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.
opportunity-solution-tree
Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to customer opportunities, possible solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when the team is unclear what to build next, when multiple opportunities compete, or before writing a…
done-blocked
Reusable reporting contract for any agent that hands work back to the pipeline. Forces ONE of two terminal statuses (DONE or BLOCKED) with a specific evidence shape. Stops vague "probably finished" and "kind of stuck" verdicts.
outcome-roadmap
Transform an output-focused roadmap (feature list) into an outcome-focused one. Rewrites initiatives as outcome statements reflecting user and business impact. Use when a roadmap lists features instead of results, when making a roadmap more strategic, or when communicating what success looks like vs what will be built.
pm-planning
Decomposition methodology for pm agent — turns an approved ARCH document into a Beads task list with explicit dependencies, time-boxes, and acceptance criteria. The pipeline can only orchestrate work it can see; this skill defines what "seeable work" looks like.
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…