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 skills/nomarj/sigil/outreach-enginenpx skills add NOMARJ/sigil --skill outreach-enginegit 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/outreach-engine)<a href="https://agentmods.dev/skills/nomarj/sigil/outreach-engine"><img src="https://agentmods.dev/badge/skills/nomarj/sigil/outreach-engine.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.00068 | $0.00809 |
| Opus 5 | $0.00034 | $0.00404 |
| Sonnet 5 | $0.00014 | $0.00162 |
| Haiku 4.5 | $0.00007 | $0.00081 |
Grade A, and why
outreach-engine 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Outreach Engine
Pre-requisites
Invoke business-context skill. Requires GTM spec and ICP doc for this product.
Motion check (hard gate)
If motion = "relationship-led":
STOP. Output:
"<Product> uses a relationship-led motion. Cold outreach will not work and
will damage the brand. The right path is warm introduction via [specific network].
Run /growth:pipeline to identify warm paths."
EXIT.
This gate is non-negotiable. Operable and Smart Settle never get cold sequences.
Sequence Design Principles
Max 3 touches. Buyers are busy. More than 3 unreplied messages is spam.
Trigger-aware. Reference the trigger event from the ICP. Generic messages get deleted.
Specific proof. One concrete fact, not "industry-leading." The 97.96% exists for a reason.
No pitch in message 1. Message 1 is pattern-interrupt + genuine value. Pitch is message 2 at earliest.
Short. Under 5 sentences per message. Mobile-readable. Busy people skim.
Australian tone. Understated. Not American hype. No "I hope this finds you well."
Sequence Format
## Outreach Sequence — <Product> / <Channel> / <ICP segment>
**Trigger:** [the event that qualifies this prospect right now]
**Channel:** [email / LinkedIn / community DM]
### Message 1 — Pattern interrupt (send day 1)
Subject: [specific, not clever]
[Body — 3-4 sentences max]
[Reference their trigger or a specific observation]
[One question or one value offer — not a pitch]
### Message 2 — Proof + ask (send day 5 if no reply)
Subject: Re: [same thread]
[Body — 3-4 sentences]
[The specific proof point — detection rate, customer result, data source]
[Clear, low-friction ask]
### Message 3 — Close or exit (send day 12 if no reply)
Subject: Re: [same thread]
[Body — 2-3 sentences]
[Acknowledge they're busy]
[Leave the door open — no guilt]
[Your value in one line for their future reference]
Sigil-specific outreach
Target: Security engineers, DevSecOps leads at companies actively using AI agents in production.
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 · 115 lines · 68 tokens per session scan A ed32aa301ba8
outreach-engine is a skill published in the GitHub repository NOMARJ/sigil (5 stars, last pushed today), licensed Apache-2.0. It adds 68 tokens to every session and 809 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
通用 SFTP 上传工具，通过自然语言触发，将本地项目文件上传到远程服务器。支持增量上传、私钥自动绑定与权限修正。.
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".
t0-orchestrator
Master orchestration for the VNX multi-terminal system. Governs receipt review, quality/risk interpretation, open-items lifecycle, PR completion decisions, and single-block dispatch creation across T1/T2/T3.
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…