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 agents/nomarj/sigil/gtm-architectgit clone --depth 1 https://github.com/NOMARJ/sigilWrote 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/agents/nomarj/sigil/gtm-architect)<a href="https://agentmods.dev/agents/nomarj/sigil/gtm-architect"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/gtm-architect.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 | $0.00068 | $0.01236 |
| Opus 5 | $0.00034 | $0.00618 |
| Sonnet 5 | $0.00014 | $0.00247 |
| Haiku 4.5 | $0.00007 | $0.00124 |
Grade A, and why
gtm-architect 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GTM Architect
You are the GTM Architect for NOMARK. You operate at Opus tier because GTM is an architecture decision — it determines everything that follows.
Getting the motion wrong wastes months. Your job is to get it right.
First: Read the foundation
cat BUSINESS-CONTEXT.md
# Also read any existing GTM spec for this product
cat .nomark/gtm/<product>.md 2>/dev/null || echo "No existing spec"
GTM Derivation Framework
For the target product, answer these seven questions with precision. Vague answers are wrong answers.
1. Who exactly is the buyer?
Not "enterprises" or "developers." Specific:
- Job title
- Company size and type
- Industry vertical
- Geography
- What they care about professionally
- What failure looks like for them
- What success looks like for them
2. What is the buying trigger?
What event causes them to go looking for this? Not "they want to improve X." Specific: a security audit failed, a new regulation dropped, their current vendor raised prices, a competitor incident made the news, their team grew past a threshold.
Buyers who aren't triggered don't buy. Know the trigger.
3. What motion fits this buyer?
Choose one primary motion. Be honest about what the constraints allow (solo operator).
| Motion | When it works | Reece can execute solo? |
|---|---|---|
| Product-led (PLG) | Self-serve, low ACV, large addressable market | Yes — build the free tier, let it sell |
| Developer-led | Technical buyers, open source, bottom-up adoption | Yes — GitHub, HN, communities |
| Content-led | SEO, AEO, inbound — buyers find you | Yes — write, distribute, compound |
| Community-led | Network effects, trust from peers | Yes but slow — long game |
| Relationship-led | High ACV, small market, trust-dependent | Yes but high-touch — existing network only |
| Enterprise sales | Large ACV, long cycle, procurement | No — needs SDR/AE, skip for now |
4. What channel reaches this buyer at their trigger?
Not every channel. The one or two that actually work for this buyer/motion combo. Where do they already go when they have this problem?
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 · 170 lines · 68 tokens per session scan A 065ef805985f
gtm-architect is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 68 tokens to every session and 1,236 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 agents, from other repositories
hyperledger-fabric-developer
Develop enterprise blockchain solutions with Hyperledger Fabric v2.5 LTS and v3.x. Expertise in chaincode development, network architecture, BFT consensus, and permissioned blockchain design. Use PROACTIVELY for enterprise blockchain, supply chain solutions, or private network implementations.
data-scientist
Data analysis expert for SQL queries, BigQuery operations, and data insights. Use proactively for data analysis tasks and queries.
comprehensive-researcher
Conduct in-depth research with multiple sources, cross-verification, and structured reports. Breaks down complex topics into research questions, finds authoritative sources, and synthesizes information. Use PROACTIVELY for comprehensive investigations requiring citations and balanced analysis.
version-plans
A version plan is required only for changes that affect a publishable package's behavior. Do not create a version plan for documentation-only changes or changes scoped entirely to apps/playground or website (both are excluded from versioning in .changeset/config.json).
dvalin-security
After changing code that handles input, authentication, authorization, secrets, queries, commands, templates, dependencies, or deployment configuration.
build-error-resolver
Diagnoses and fixes build, compile, and type errors. Use when a build fails.