Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/teachskillofskills-ai/ContentForge-techshunpx agentmods add skills/teachskillofskills-ai/contentforge-techshu/cf-integrationsWrote 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/teachskillofskills-ai/contentforge-techshu/cf-integrations)<a href="https://agentmods.dev/skills/teachskillofskills-ai/contentforge-techshu/cf-integrations"><img src="https://agentmods.dev/badge/skills/teachskillofskills-ai/contentforge-techshu/cf-integrations/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/teachskillofskills-ai/contentforge-techshu/cf-integrations"><img src="https://agentmods.dev/badge/skills/teachskillofskills-ai/contentforge-techshu/cf-integrations.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.00141 | $0.01771 |
| Opus 5 | $0.00071 | $0.00886 |
| Sonnet 5 | $0.00028 | $0.00354 |
| Haiku 4.5 | $0.00014 | $0.00177 |
Grade A, and why
cf-integrations 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 8d 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
100% identical to cf-integrations — 0 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/contentforge:cf-integrations — Integration Status Dashboard
Show the complete integration status for your ContentForge installation — configured vs available connectors, grouped by category, with workflow impact analysis and quick-win recommendations.
The ground truth about connectors
ContentForge ships with an empty .mcp.json ("mcpServers": {}) by design (v3.9.0 Cowork-safety decision). On a fresh install, expect 0 connectors configured (or 1-2 if the platform injects its own integrations). Nothing is pre-wired.
Every number in the dashboard must come from the live script output. Never render counts, percentages, or connected/available labels that are not present in the JSON returned by scripts/connector-status.py. Do not copy numbers from the example in this file.
When to Use
Use /contentforge:cf-integrations when:
- You just installed ContentForge and want to see what's connected
- You're troubleshooting why a skill can't reach an external service
- You want to know which connectors to add next for maximum workflow coverage
- You need a quick overview before onboarding a new team member
- You're planning which integrations to set up for a new project
What This Command Does
- Scan All Connectors — Run the status script; it checks the connector registry against your
.mcp.jsonand environment variables - Build Status Dashboard — Group results by category with clear configured/available distinction
- Calculate Coverage — Report exactly the totals the script returns
- Recommend Quick Wins — Highlight the top 3 not-yet-configured connectors by workflow impact
- Surface Category Gaps — Identify categories with zero coverage
- Provide Next Steps — For each recommendation, point to
/contentforge:cf-connect <name>
Required Inputs
Optional:
- Category filter — Show only a specific category (e.g.,
--category=seo) - Show filter —
connected,available, orall(default:all)
What Happens
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.
- 8d ago First seen · 149 lines · 141 tokens per session scan A 167b74cb226d
cf-integrations is a skill published in the GitHub repository teachskillofskills-ai/ContentForge-techshu (1 stars, last pushed 19d ago), licensed MIT. It adds 141 tokens to every session and 1,771 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cf-integrations, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
meta-tags-optimizer
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
sxo
Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
security
Enforce Elixir/Phoenix security — auth, OAuth, sessions, CSRF, XSS, SQL injection, input validation, secrets. Use when editing auth files, login flows, RBAC, or API keys.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.