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/ecorkran/context-forge/cf-onboardnpx skills add ecorkran/context-forge --skill cf-onboardgit clone --depth 1 https://github.com/ecorkran/context-forgeWrote 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/ecorkran/context-forge/cf-onboard)<a href="https://agentmods.dev/skills/ecorkran/context-forge/cf-onboard"><img src="https://agentmods.dev/badge/skills/ecorkran/context-forge/cf-onboard.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.00036 | $0.00568 |
| Opus 5 | $0.00018 | $0.00284 |
| Sonnet 5 | $0.00007 | $0.00114 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
cf-onboard 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 3d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Forge Onboard
You are guiding a user through Context Forge project onboarding. Follow these steps in order — skip any step whose precondition is already met.
Step 1 — Detect existing project
Run cf project list and check whether a project is already registered at
the current working directory.
- If a project exists at this path → skip to Step 3.
- If no project exists → continue to Step 2.
Step 2 — Create project
Ask the user what they'd like to name their project. If they provided a name with the request, use that. If the user declines to choose, default to the current directory name.
Run cf init <name>. This single command handles everything: git
initialization, project registration, guide installation, command/skill
installation, and IDE setup. After cf init completes, continue to Step 3.
Important: Do not rely on environment context (like "Is a git
repository") to determine git status — cf init checks the actual directory
and handles git initialization itself.
If the Context Forge MCP server is configured and shell access is
unavailable, fall back to its project_create tool (with name and
projectPath set to the CWD) followed by guide_install. The MCP fallback
cannot initialize git — if the directory is not a git repository, inform the
user they need to run git init first.
Step 3 — Transition to concept discussion
The project is set up. Run cf build and use the output as your working
context to begin the Phase 0 (Concept) conversation.
Begin by asking the user to describe what they want to build. Guide them through the concept exploration naturally — the context prompt provides the structure. The goal is a concept document at the end of this conversation.
Step 4 — Mention ongoing guidance
After the concept conversation concludes (or if the user wants to pause),
mention: "You can run cf next (or the cf-next skill) anytime to see what
to do next. It adapts as your project progresses."
Notes
- If an MCP tool call fails, fall back to the CLI equivalent.
- If the user already has a project but is in a later phase (not Phase 0),
acknowledge this and suggest
cf nextinstead of starting a concept discussion. - Keep the conversation natural. This is onboarding, not a checklist. Adapt to what the user is telling you.
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.
- 3d ago First seen · 62 lines · 36 tokens per session scan A b3e6b7bd4c4d
cf-onboard is a skill published in the GitHub repository ecorkran/context-forge (5 stars, last pushed 23d ago), licensed MIT. It adds 36 tokens to every session and 568 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-31.
Other skills, from other repositories
Technical Debt Tracking with PMAT
Tracks and manages technical debt using PMAT (Pragmatic AI Labs MCP Agent Toolkit). Use this skill when: User asks about technical debt, TODO comments, or code quality issues Planning sprint work and need to prioritize debt repayment Conducting code audits or technical debt assessments Tracking debt accumulation…
issue_approve
Approve issue to transition to next workflow status.
pipefy-pipes-and-cards
Use this skill when the user wants to read, create, update, or delete pipes, phases, phase fields, labels, cards, comments, or field conditions. Covers 40 MCP tools for the core pipe and card lifecycle. Use the seed-pipe-across-phases workflow when populating empty phases for demos or QA.
implementation_needs_rework
Return issue to plan-ready status for re-implementation after major review issues.
pipefy-process-design
Use this skill ONLY when the user explicitly asks for help designing or architecting a process ("help me design", "what's the best structure", "how do I organize this flow?"). For direct execution requests ("create a pipe for X", "build a reimbursement process", or any message with a detailed spec), skip this skill…
github-todo-triage
Use this skill in this repository when asked to fetch, review, triage, or update todos from GitHub issues and pull requests, especially for xing5/mcp-google-sheets. It defines the local workflow for refreshing GitHub state, reviewing new work, prioritizing next actions, and maintaining the repo todo status ledger.