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/forefy/.context/variant-tablenpx skills add forefy/.context --skill variant-tablegit clone --depth 1 https://github.com/forefy/.contextWrote 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/forefy/.context/variant-table)<a href="https://agentmods.dev/skills/forefy/.context/variant-table"><img src="https://agentmods.dev/badge/skills/forefy/.context/variant-table.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 | $0.00038 | $0.00819 |
| Opus 5 | $0.00019 | $0.00409 |
| Sonnet 5 | $0.00008 | $0.00164 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
variant-table 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Variant Table
Turn a piece of draft copy into a side-by-side comparison table so the user can compare wording options per unit and pick.
When to use
Any time the user is refining wording and would benefit from seeing distinct options laid out rather than a single rewrite. Works for any content type: social posts, headlines, taglines, email lines, bios, CTAs, microcopy, doc sentences, spec bullets, commit messages. Content-agnostic - never assume it is a LinkedIn post.
Output format
A markdown table. One row per logical unit of the source. Columns:
| # | Current | A - | B - | C - | My pick |
- # - unit index plus a 1-2 word role label in parens, e.g.
1 (hook),4 (CTA),2 (bullet). The label names the unit's job, inferred from the content. - Current - the user's existing text for that unit, verbatim. If the user gave no existing draft, leave a short placeholder or omit this column.
- A / B / C - three rewrites. See the distinctness rule below. Rename the angle after the dash per row to whatever actually differs (e.g.
A - blunt,B - contrarian,C - technical). - My pick - one recommendation for that row, in bold. It may be one of A/B/C, the current text ("keep"), or a fresh hybrid. Add a terse parenthetical reason only when it aids the choice.
The distinctness rule (most important)
The three variations must differ in approach, not just word swaps. Before writing a row, pick three different axes and commit one variation to each. Draw from axes like:
- tone: blunt / playful / formal / contrarian
- structure: statement / question / fragment / story-fragment
- angle: pain-first / benefit-first / curiosity-gap / social-proof / technical-precision
- length: terse vs flowing
If two variations could be swapped without a reader noticing a shift in strategy, they are too similar - rewrite one. Label each column with the axis it took so the contrast is legible.
How to segment
Split the source into the units the user is actually deciding on:
- prose → paragraphs (or sentences if they're iterating sentence-level)
- list → bullets
- headline + subhead → separate rows
- table/form → cells or fields
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 · 60 lines · 38 tokens per session scan A 510747ab3963
variant-table is a skill published in the GitHub repository forefy/.context (141 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 819 once invoked, about $0.0002 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-30.
Other skills, from other repositories
eresus-manual-security-audit
Elite manual security code review skill for deep, adversarial vulnerability hunting and exploit-chain discovery. Trigger when the user asks to: "do a deep security audit", "manual code review", "find exploit chains", "hunt for logic bugs", "red-team this codebase", "do an offensive security review", "review this like…
eresus-sast-scanner
General-purpose Static Application Security Testing (SAST) skill for code vulnerability analysis. Trigger when the user asks to: "analyze code for vulnerabilities", "review code security", "find security bugs", "do a SAST scan", "check for [vulnerability type] in code", "audit source code", or requests a security code…
eresus-php-audit
Deep PHP-specific security audit skill covering injection, deserialization, file operations, auth bypass, POP chain discovery, and CMS-specific patterns. Trigger when auditing PHP code: "audit this PHP app", "find PHP security issues", "check Laravel/WordPress for vulnerabilities", "PHP SAST review", "check for PHP…
eresus-python-audit
Deep Python-specific security audit skill with 50+ vulnerability class coverage across 7 categories. Trigger when auditing Python code: "audit this Python app", "find Python security issues", "check Flask/Django for vulnerabilities", "Python SAST review", "check for pickle vulnerabilities", "review this FastAPI code".…
eresus-pr-security-review
Security-focused pull request and diff review skill for finding newly introduced vulnerabilities, risky regressions, and missing security tests in changed code. Trigger when the user asks to: "review this PR for security", "check this diff for vulns", "do a security code review", "audit changed files", or wants…
eresus-remediator
Security remediation skill for fixing confirmed or likely SAST findings in source code. Trigger when the user asks to: "fix a vulnerability", "patch this security bug", "remediate SAST findings", "harden this endpoint", "make this auth flow safe", or wants code changes that remove a confirmed security issue while…