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 commands/aneja5/forge-skills/gtmgit clone --depth 1 https://github.com/aneja5/forge-skillsWrote 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/aneja5/forge-skills/gtm)<a href="https://agentmods.dev/commands/aneja5/forge-skills/gtm"><img src="https://agentmods.dev/badge/commands/aneja5/forge-skills/gtm.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.00017 | $0.00149 |
| Opus 5 | $0.00009 | $0.00075 |
| Sonnet 5 | $0.00003 | $0.00030 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
gtm 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.
What it actually says
Invoke the forge-skills:gtm-strategy skill.
Read .forge/prd.md and .forge/competitive.md. If competitive analysis doesn't exist, tell the user to run /compete first.
Define the ICP as a named persona (title + company profile, not "SMBs"). Identify the wedge feature — one capability that gets you in the door. Design a pilot program with specific success criteria. Map sales channels with motions and CAC estimates. Build an ROI calculator with conservative numbers. Create a case study template with quantified before/after.
After writing: "GTM strategy written to .forge/gtm.md."
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 · 17 lines · 17 tokens per session scan A ccdcc634189a
gtm is a command published in the GitHub repository aneja5/forge-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 149 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
feature
Implement a ready-for-agent feature ticket in this checkout. Do not expand the ask.
bug
Reproduce then TDD-fix a ready-for-agent bug ticket in this checkout. Web bugs get a browser repro first.
ci
Watch gh pr checks until green and fix failures on this branch. Do not merge.
docs
Docs-only change for a ready-for-agent ticket. No application code.
lead
Tech lead: classify, quiz, ticket on the owning repo, dispatch. Do not implement.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.