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 NOMARJ/sigil --skill product-marketing-contextgit 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/skills/nomarj/sigil/product-marketing-context)<a href="https://agentmods.dev/skills/nomarj/sigil/product-marketing-context"><img src="https://agentmods.dev/badge/skills/nomarj/sigil/product-marketing-context/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/nomarj/sigil/product-marketing-context"><img src="https://agentmods.dev/badge/skills/nomarj/sigil/product-marketing-context.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.00090 | $0.01481 |
| Opus 5 | $0.00045 | $0.00740 |
| Sonnet 5 | $0.00018 | $0.00296 |
| Haiku 4.5 | $0.00009 | $0.00148 |
Grade A, and why
product-marketing-context 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 11d 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Marketing Context
You help users create and maintain product marketing context documents. This captures foundational positioning and messaging information that other marketing/growth/SEO skills reference, so users don't repeat themselves.
File Locations
The context document integrates into the NOMARK context hierarchy:
- Per-product GTM context:
.nomark/gtm/<product>.md— lives in the project repo - Portfolio-level context:
BUSINESS-CONTEXT.md— portfolio strategy and brand voice - Project-level context:
SOLUTION.md— product-specific positioning
This skill creates/updates the per-product GTM context file.
Workflow
Step 1: Check for Existing Context
Check for existing context files in this order:
.nomark/gtm/<product>.md(current standard).agents/product-marketing-context.md(legacy location).claude/product-marketing-context.md(older legacy)
If found in legacy location, offer to migrate to .nomark/gtm/.
Step 2: Gather Information
Option 1 — Auto-draft from codebase (recommended): Study the repo — README, landing pages, marketing copy, package.json, docs — and draft a V1. The user reviews, corrects, and fills gaps.
Option 2 — Start from scratch: Walk through each section conversationally, one at a time.
Push for verbatim customer language — exact phrases are more valuable than polished descriptions.
Step 3: Create the Document
Sections to Capture
1. Product Overview
- One-line description
- What it does (2–3 sentences)
- Product category
- Product type (SaaS, marketplace, service, etc.)
- Business model and pricing
2. Target Audience
- Target company type (industry, size, stage)
- Target decision-makers (roles, departments)
- Primary use case
- Jobs to be done (2–3)
- Specific use cases or scenarios
3. Personas (B2B)
For each stakeholder: User, Champion, Decision Maker, Financial Buyer, Technical Influencer — what they care about, their challenge, and the value you promise them.
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.
- 11d ago First seen · 232 lines · 90 tokens per session scan A f0c32d0073c7
product-marketing-context is a skill published in the GitHub repository NOMARJ/sigil (5 stars, last pushed 5d ago), licensed Apache-2.0. It adds 90 tokens to every session and 1,481 once invoked, about $0.0005 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 skills, from other repositories
sftp-cc
A natural-language SFTP tool for uploading local project files to a remote server. SFTP is a secure way to transfer files, and this tool supports incremental uploads, private-key binding, and permission fixes.
regex-mastery
Use this skill when writing regular expressions, debugging pattern matching,optimizing regex performance, or implementing text validation. Triggers on regex, regular expressions, pattern matching, lookahead, lookbehind, named groups, capture groups, backreferences, and any task requiring text pattern matching.
devtools-event-client
Create typed EventClient for a library. Define event maps with typed payloads, pluginId auto-prepend namespacing, emit()/on()/onAll()/onAllPluginEvents() API. Connection lifecycle (5 retries, 300ms), event queuing, enabled/disabled state, SSR fallbacks, singleton pattern. Unique pluginId requirement to avoid event…
jk
Manage Jenkins controllers with jk, including jobs, runs, logs, artifacts, credentials, nodes, queues, and plugins.
assess-patch-risk
Assess an immutable patch artifact's program impact, regression risk, and auto-merge eligibility. Use for generated patch files, provider pull-request diffs, or commit ranges when reviewers need evidence about affected runtime paths, contracts, tests, and recoverability. This skill is read-only and does not generate…
shepherd-start
Open a focused investigation session for one bug: pull its full tracker detail, load past lessons and triage history, and produce an investigation plan. Use when starting work on a single ticket, after /shepherd-sync has built the backlog.