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-connectWrote 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-connect)<a href="https://agentmods.dev/skills/teachskillofskills-ai/contentforge-techshu/cf-connect"><img src="https://agentmods.dev/badge/skills/teachskillofskills-ai/contentforge-techshu/cf-connect/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-connect"><img src="https://agentmods.dev/badge/skills/teachskillofskills-ai/contentforge-techshu/cf-connect.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.00170 | $0.03177 |
| Opus 5 | $0.00085 | $0.01588 |
| Sonnet 5 | $0.00034 | $0.00635 |
| Haiku 4.5 | $0.00017 | $0.00318 |
Grade A, and why
cf-connect 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 10d 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-connect — 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/contentforge:cf-connect — Guided Connector Setup
Set up a specific MCP integration for ContentForge with step-by-step instructions tailored to the connector's transport type. Handles HTTP connectors (OAuth-based), npx connectors (API keys, environment variables, .mcp.json entry), unknown connector names (fuzzy matching), and post-setup verification.
The ground truth about connectors
ContentForge ships with an empty .mcp.json ("mcpServers": {}). This is deliberate (v3.9.0 Cowork-safety decision): no connector auto-connects when the plugin is installed. Every connector is opt-in — the user adds it to .mcp.json (or connects it at the platform level in Cowork/Desktop Settings → Integrations).
Never claim a connector is pre-wired or already connected. All status claims must come from running python scripts/connector-status.py — never from this file or from memory.
When to Use
Use /contentforge:cf-connect <name> when:
- You want to connect a specific service (e.g.,
/contentforge:cf-connect wordpress) - A skill told you a connector is missing and suggested using this command
- You're setting up a new ContentForge installation and configuring integrations
- You need the exact environment variables and
.mcp.jsonentry for an npx connector - You want to verify an existing connector is working correctly
What This Command Does
- Look Up Connector — Find the connector in the registry, handle typos and close matches
- Check Current Status — Determine if already configured or needs setup
- Present Setup Instructions — Tailored to transport type (HTTP vs npx)
- Guide Credential Acquisition — Where to get API keys, which permissions to set
- Provide .mcp.json Entry — Ready-to-paste configuration
- Verify After Setup — Confirm environment variables are set and configuration is valid
Required Inputs
Required:
- Connector name — The service to connect (e.g.,
notion,wordpress,google-sheets,canva) - Fuzzy matching is supported:
wpmatcheswordpress,gsheetsmatchesgoogle-sheets,gamatchesgoogle-analytics
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.
- 10d ago First seen · 264 lines · 170 tokens per session scan A 258de888be70
cf-connect is a skill published in the GitHub repository teachskillofskills-ai/ContentForge-techshu (1 stars, last pushed 21d ago), licensed MIT. It adds 170 tokens to every session and 3,177 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cf-connect, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
scrapecreators-api
Scrape and extract public data from 27+ social media platforms using the ScrapeCreators REST API. Covers TikTok, Instagram, YouTube, LinkedIn, Facebook, Twitter/X, Reddit, Threads, Bluesky, Pinterest, Snapchat, Twitch, Kick, Truth Social, TikTok Shop, Google, and link-in-bio services (Linktree, Komi, Pillar, Linkbio…
ash-framework
Ash Framework — resources, actions, policies, aggregates, calculations, AshPhoenix.Form, LiveView, migrations. Use when generating resources via mix ash.codegen, editing changes, checks, types, validations, or domain code interfaces.
liveview-patterns
Build LiveView: async data (assignasync), PubSub (check connected?), phx-change events, form components/modals/uploads, streams for lists, livepatch. Use when handling interactions, debugging events, or tracking Presence.
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.
deploy
Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays. Use when configuring Fly.io, Docker, CI/CD, health checks, or production migrations.
oban
Oban job processing — workers, perform/1 (OSS) and process/1 (Pro), queues, cron, retries, unique jobs, idempotency, Oban Pro (Workflow, Batch, Chunk, Smart Engine), Testing. Use when writing Oban workers, queue config, or debugging jobs.