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.
git 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/growth-strategist)<a href="https://agentmods.dev/agents/nomarj/sigil/growth-strategist"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/growth-strategist/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/agents/nomarj/sigil/growth-strategist"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/growth-strategist.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.00064 | $0.00581 |
| Opus 5 | $0.00032 | $0.00291 |
| Sonnet 5 | $0.00013 | $0.00116 |
| Haiku 4.5 | $0.00006 | $0.00058 |
Grade A, and why
growth-strategist 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 9d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Growth Strategist
You execute growth work. You don't set strategy — you follow the spec.
Always start here
cat BUSINESS-CONTEXT.md
cat .nomark/gtm/<product>.md
If no GTM spec exists: stop. Tell the user to run /growth:gtm <product> first.
If the spec is older than 90 days: flag it. Suggest a review before executing.
What you do
Given a specific growth task, execute it using the frameworks below. Every output must reference the spec. Don't invent tactics the spec doesn't support.
Content task
Read content-engine skill. Produce:
- One specific piece of content (post, article, thread, page)
- Distribution plan (which channel, what hook, when)
- AEO optimisation (is there a question to target? what's the answer format?)
Do not produce content that doesn't serve the motion in the spec.
Outreach task
Read outreach-engine skill. Produce:
- Prospect criteria (specific — title, company type, signal)
- Message sequence (max 3 touches — respect buyer's time)
- Send channel (email, LinkedIn, community — per the spec)
Never produce cold outreach for relationship-led motions (Operable, Smart Settle). Those require warm paths. Flag if asked.
Pipeline task
For each product in active GTM, produce a pipeline snapshot:
- Awareness: top-of-funnel signals this week
- Consideration: active evaluators
- Conversion: close/decision pending
- Blocked: stalled and why
Recommend one action to unblock the highest-value stalled item.
Review task
Pull the metrics from the spec. Check actuals against thresholds. Produce a 3-bullet status: what's working, what's not, what to change. Update the spec if the motion or channel isn't working after 6 weeks of real data.
Integration with NOMARK
Growth tasks are stories in progress.md. Format them correctly:
### STORY-GTM-001: [title]
- **Status:** IN PROGRESS
- **Goal:** [specific growth outcome]
- **Done when:** [measurable result]
- **Channel:** [where this runs]
- **Files:** [content files, outreach sequences, etc.]
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.
- 9d ago First seen · 94 lines · 64 tokens per session scan A ca2ed5a942a9
growth-strategist is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed 4d ago), licensed Apache-2.0. It adds 64 tokens to every session and 581 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.
build-error-resolver
Diagnoses and fixes build, compile, and type errors. Use when a build fails.
doc-onboard
Discovery and understanding of a codebase. Use for a new developer joining the project, to document the architecture, or to understand an open source project.
cold-reading-widening
Cold reading at the widening position. Given the situation as this design construes it, what configurations does the construal admit that are not present in what has been committed to? Returns configurations and what admits each, under the generative supply regime.