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 business-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/business-context)<a href="https://agentmods.dev/skills/nomarj/sigil/business-context"><img src="https://agentmods.dev/badge/skills/nomarj/sigil/business-context.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.00066 | $0.00643 |
| Opus 5 | $0.00033 | $0.00321 |
| Sonnet 5 | $0.00013 | $0.00129 |
| Haiku 4.5 | $0.00007 | $0.00064 |
Grade A, and why
business-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 6d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business Context — Foundation Skill
You are the foundation layer. Every growth and business-strategy skill invokes you first.
What you do
- Find and read the project's SOLUTION.md (primary context)
- Identify the target product from the user's request
- Read
.nomark/gtm/<product>.mdif it exists (GTM supplement) - Fall back to
BUSINESS-CONTEXT.mdif no SOLUTION.md found (portfolio level) - Return a compact context summary for use by the calling skill
Context search order
1. SOLUTION.md ← per-project, highest priority
2. .nomark/gtm/<product>.md ← GTM specifics
3. BUSINESS-CONTEXT.md ← portfolio-level fallback
4. User input ← last resort
Context summary format
Project: <name>
Product: <product name from SOLUTION.md Part I or BUSINESS-CONTEXT.md>
Stage: <status from SOLUTION.md or inferred>
Motion: <primary GTM motion>
Buyer: <specific buyer description>
Channel: <primary channel>
Core message: <one sentence>
Brand voice: <from BUSINESS-CONTEXT.md or SOLUTION.md>
Constraints: <from SOLUTION.md Part VI or BUSINESS-CONTEXT.md>
Fixed specs: <non-negotiable items from SOLUTION.md Part II>
Variable specs: <open questions / assumptions still being tested>
Context source: SOLUTION.md / BUSINESS-CONTEXT.md / user-provided
GTM spec: [present / not yet created]
If SOLUTION.md doesn't exist
Check for BUSINESS-CONTEXT.md. If found, extract the relevant product section and flag: "No SOLUTION.md for this project. Using portfolio-level context from BUSINESS-CONTEXT.md. For sharper results, create a SOLUTION.md — I can generate one from what you tell me."
If neither exists
Tell the user: "No project context found. I need to know what you're building before running growth work. Give me a quick summary and I'll load context from that — or I can generate a SOLUTION.md template for you to fill in."
If GTM spec doesn't exist for this product
Return the context from SOLUTION.md / BUSINESS-CONTEXT.md and flag:
"No GTM spec for . Recommend running /growth:gtm <product> before executing.
Proceeding with available context only."
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.
- 6d ago First seen · 73 lines · 66 tokens per session scan A e0388a0a9827
business-context is a skill published in the GitHub repository NOMARJ/sigil (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 66 tokens to every session and 643 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 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
Jenkins CLI for controllers. Use when users need to manage jobs, pipelines, config.xml, runs, logs, artifacts, credentials, nodes, or queues in Jenkins. Triggers include "jenkins", "jk", "pipeline", "build", "job create", "job config", "config.xml", "run logs", "jenkins credentials", "jenkins node".
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.