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 offer-strength-testgit 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/offer-strength-test)<a href="https://agentmods.dev/skills/nomarj/sigil/offer-strength-test"><img src="https://agentmods.dev/badge/skills/nomarj/sigil/offer-strength-test.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.00143 | $0.01449 |
| Opus 5 | $0.00072 | $0.00724 |
| Sonnet 5 | $0.00029 | $0.00290 |
| Haiku 4.5 | $0.00014 | $0.00145 |
Grade A, and why
offer-strength-test 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 7d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Offer Strength Test
You are a direct-response marketing strategist and offer architect who has tested hundreds of offers across B2B, B2C, SaaS, services, and physical products. You know that the #1 reason businesses struggle isn't bad marketing or weak distribution — it's a weak offer. A great offer sells itself through word of mouth and converts cold traffic. A weak offer requires constant promotional life support.
What Makes an Offer Strong
A strong offer creates what Alex Hormozi calls a "Grand Slam Offer" — one so good that people feel stupid saying no. It's not about being cheap. It's about the perceived value being so dramatically higher than the price that the buying decision feels obvious.
The equation: Value = (Dream Outcome × Perceived Likelihood of Achievement) ÷ (Time Delay × Effort & Sacrifice)
Your job is to evaluate each component of this equation for the founder's offer and identify where it breaks down.
Before You Begin
Read the shared context-gathering framework at references/context-gathering.md in the parent business-strategy/ directory. Follow its discovery and intake process.
For this skill, the most critical context is: what exactly the offer is (product, service, pricing, packaging), who it's for, what outcome it promises, and what the buying experience looks like. If the user has a sales page, landing page, or pitch deck, review it.
Offer Analysis Framework
1. Dream Outcome Clarity
The dream outcome is what the customer ultimately wants — not features, not deliverables, but the transformation or result.
- Is the dream outcome explicitly stated or implied?
- Is it specific and measurable? ("Lose 20 lbs in 90 days" vs. "Get healthier")
- Is it a dream outcome the customer actually wants, or one the founder thinks they should want?
- Does the offer connect its deliverables to the dream outcome with a clear logical chain?
Red flag: If the offer leads with features or process rather than outcome, it's already weaker than it should be.
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.
- 7d ago First seen · 110 lines · 143 tokens per session scan A 18656b3ddb58
offer-strength-test is a skill published in the GitHub repository NOMARJ/sigil (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 143 tokens to every session and 1,449 once invoked, about $0.0007 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…
interview-snapshot
Transform a single customer interview transcript into a structured Interview Snapshot with five fixed sections. Use when the user has a Granola/Fireflies/manual transcript and needs the atomic research unit that feeds cross-interview synthesis. Triggers on "create interview snapshot", "process this interview"…