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 Jamkris/everything-gemini-code --skill content-enginegit clone --depth 1 https://github.com/Jamkris/everything-gemini-codeWrote 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/jamkris/everything-gemini-code/content-engine)<a href="https://agentmods.dev/skills/jamkris/everything-gemini-code/content-engine"><img src="https://agentmods.dev/badge/skills/jamkris/everything-gemini-code/content-engine/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jamkris/everything-gemini-code/content-engine"><img src="https://agentmods.dev/badge/skills/jamkris/everything-gemini-code/content-engine.svg" alt="Reviewed on agentmods" width="80" 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.00055 | $0.00577 |
| Opus 5.5 | $0.00022 | $0.00231 |
| Sonnet 5.5 | $0.00011 | $0.00115 |
| Haiku 4.5 | $0.00006 | $0.00058 |
Grade A, and why
content-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 1mo 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.
This is a copy
95% identical to content-engine — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Engine
Turn one idea into strong, platform-native content instead of posting the same thing everywhere.
When to Use
- writing X posts or threads
- drafting LinkedIn posts or launch updates
- scripting short-form video or YouTube explainers
- repurposing articles, podcasts, demos, or docs into social content
- building a lightweight content plan around a launch, milestone, or theme
First Questions
Clarify:
- source asset: what are we adapting from
- audience: builders, investors, customers, operators, or general audience
- platform: X, LinkedIn, TikTok, YouTube, newsletter, or multi-platform
- goal: awareness, conversion, recruiting, authority, launch support, or engagement
Core Rules
- Adapt for the platform. Do not cross-post the same copy.
- Hooks matter more than summaries.
- Every post should carry one clear idea.
- Use specifics over slogans.
- Keep the ask small and clear.
Platform Guidance
X
- open fast
- one idea per post or per tweet in a thread
- keep links out of the main body unless necessary
- avoid hashtag spam
- strong first line
- short paragraphs
- more explicit framing around lessons, results, and takeaways
TikTok / Short Video
- first 3 seconds must interrupt attention
- script around visuals, not just narration
- one demo, one claim, one CTA
YouTube
- show the result early
- structure by chapter
- refresh the visual every 20-30 seconds
Newsletter
- deliver one clear lens, not a bundle of unrelated items
- make section titles skimmable
- keep the opening paragraph doing real work
Repurposing Flow
Default cascade:
- anchor asset: article, video, demo, memo, or launch doc
- extract 3-7 atomic ideas
- write platform-native variants
- trim repetition across outputs
- align CTAs with platform intent
Deliverables
When asked for a campaign, return:
- the core angle
- platform-specific drafts
- optional posting order
- optional CTA variants
- any missing inputs needed before publishing
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.
- 1mo ago First seen · 89 lines · 55 tokens per session scan A b84a55f8fd29
content-engine is a skill published in the GitHub repository Jamkris/everything-gemini-code (90 stars, last pushed 4mo ago), licensed MIT. It adds 55 tokens to every session and 577 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to content-engine, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
redteam
Expertise in offensive security research, vulnerability analysis, CMS-focused application testing, and red team operations.
redteam-cms
Focused methodology for authorized CMS fingerprinting, component inventory, misconfiguration review, and vulnerability validation.
redteam-exploit-validation
Focused workflow for validating exploitability safely and turning candidate issues into reproducible, bounded proof.
redteam-recon
Focused reconnaissance workflow for authorized security assessments, bug bounty triage, lab targets, and CTF infrastructure.
redteam-reporting
Focused reporting workflow for converting verified red-team work into clear, reproducible assessment artifacts.
redteam-source-audit
Focused source-code security review workflow for web applications, CMS extensions, APIs, and supporting services.