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/voxtechnologies/anty-framework/content-rulesnpx skills add VoxTechnologies/anty-framework --skill content-rulesgit clone --depth 1 https://github.com/VoxTechnologies/anty-frameworkWhat 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 | $0.00056 | $0.01153 |
| Opus 5 | $0.00028 | $0.00576 |
| Sonnet 5 | $0.00011 | $0.00231 |
| Haiku 4.5 | $0.00006 | $0.00115 |
Grade A, and why
content-rules 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- content-rules — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Rules
When to Apply
- Generating any marketing or sales content
- Reviewing drafts for quality
- Creating sales support materials
- When content feels generic or product-centric
- Preparing materials for pipeline Steps 5-7
Core Framework
Customer-as-Protagonist
The customer is the hero. The product is the tool that helps them succeed.
Detection rule: If content contains >30% "we" statements -> rewrite.
BAD (company-centric):
"We built an innovative AI platform that revolutionizes..."
"Our product features include..."
"We are excited to announce..."
GOOD (customer-centric):
"CTOs at seed-stage startups waste 10h/week on manual reporting.
[Product] cuts that to 30 minutes."
"Your sales team closes 3x more demos when..."
"Imagine opening your dashboard Monday morning and seeing..."
Inflated Language Filter
Detect and replace hollow superlatives with concrete value:
| Inflated | Replace With |
|---|---|
| "Revolutionary" | Specific improvement: "reduces report time from 10h to 30min" |
| "Game-changing" | Concrete outcome: "3x demo close rate" |
| "Best-in-class" | Comparative data: "28% response vs 8% industry avg" |
| "Cutting-edge" | Specific capability: "processes 10K leads in under 2 min" |
| "Innovative" | What it actually does differently |
| "World-class" | Specific benchmark or achievement |
| "Seamless" | Describe the actual experience |
| "Powerful" | Quantify the capability |
Rule: If you can't replace the adjective with a number or specific outcome, the claim is hollow. Remove it.
Precision Targeting
Content must target a specific persona. Never "everyone."
BAD: "Perfect for businesses of all sizes"
GOOD: "Built for CTOs at 10-50 person B2B SaaS companies
who don't have a dedicated data team"
Test: Can you name 3 specific people who fit this description? If not, the targeting is too vague.
Sell Results, Not Products
Frame all messaging around customer outcomes, never product features.
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.
- 2d ago First seen · 135 lines · 56 tokens per session scan A 9a01f8598b45
content-rules is a skill published in the GitHub repository VoxTechnologies/anty-framework (6 stars, last pushed 4mo ago), licensed MIT. It adds 56 tokens to every session and 1,153 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
choice-architecture
Nudge-based choice architecture for 3-option selection UI — smart default vs active choice, outcome mapping, channel factors, RECAP, operational transparency with source attribution, post-decision reinforcement, error-forgiving undo, peak-end session design, user contribution acknowledgment. Use when presenting…
culture-map
Erin Meyer's Culture Map with 8 dimensions, 5 launch presets (US, JP, DE, UK, FR), Layer A agent-user adaptation, Layer B content-target market adaptation, and anti-sycophancy tone calibration per culture. Use when adapting communication style to the founder's culture, localizing content for target markets, or when…
failure-essence
4 strategic failure patterns from Essence of Failure — dual-objective trap (conflict stress test), strategic ambiguity (operationalizability test), withdrawal decision protocol (pre-committed stop conditions, re-present biweekly), assumption provenance auditing (source, verification, load-bearing flag, sample size).…
pipeline
Cash Machine 10-step B2B sales pipeline with 3 presets, verifiable checkpoints per step, trajectory logging, bottleneck detection with utilization formula, lead qualification gate (BANT 6-criteria), pipeline velocity and stall detection (2x threshold), two-tier probability scoring, BBS tracking, end-of-quarter…
plan-b
Plan B framework — 6 environmental forces monitoring, pre-mortem 5-step process, scenario planning with auto-trigger points, Devil's Advocate on every proposal, 100-day gate reviews, S-curve awareness, 5 hurdles to Plan B execution, boomerang prevention. Use when preparing contingencies, monitoring environmental…
quest-interview
QUEST Socratic interview methodology — beginner stance, empathic neutrality, downward/upward questioning, echo questions, concept identification, permission checks, critical point pursuit, anti-pattern safeguards, resolution imbalance diagnostic, workaround discovery, painkiller vs vitamin test, locally famous test.…