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 NimbleBrainInc/mcp-folk --skill mcp_folkgit clone --depth 1 https://github.com/NimbleBrainInc/mcp-folkWrote 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/nimblebraininc/mcp-folk/mcp_folk)<a href="https://agentmods.dev/skills/nimblebraininc/mcp-folk/mcp_folk"><img src="https://agentmods.dev/badge/skills/nimblebraininc/mcp-folk/mcp_folk/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/nimblebraininc/mcp-folk/mcp_folk"><img src="https://agentmods.dev/badge/skills/nimblebraininc/mcp-folk/mcp_folk.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.00000 | $0.01072 |
| Opus 5 | $0.00000 | $0.00536 |
| Sonnet 5 | $0.00000 | $0.00214 |
| Haiku 4.5 | $0.00000 | $0.00107 |
Grade A, and why
mcp_folk 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 9d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Folk CRM Integration
ID Format
Folk IDs are a short prefix + UUID v4: per_xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
The find_person tool returns IDs in this exact format:
{
"found": true,
"matches": [
{"id": "per_xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "name": "Full Name", "email": "..."}
],
"total": 1
}
You must copy the id value exactly from the search result. If you do not have an ID from a search result in the current conversation, call find_person or find_company again.
Quick Start: Querying a Group
When user asks about contacts in a group, pipeline, or filtered by status:
User: "Show leads in Demo Management with status Follow up 1"
Step 1: find_people_in_group("Demo Management", status="Follow up 1")
Done. One call.
Do NOT start with find_person or browse_people for group queries.
Situational Handling
Situation: User asks about a group, pipeline, view, or status
Trigger phrases: "in the X group", "leads with status Y", "show me the pipeline", "Demo Management", "follow-up list"
Required action: Use group tools directly.
Step 1: find_people_in_group(group_name, status=...)
If you don't know the group name, call list_groups() first.
If looking for companies in a group, use find_companies_in_group instead.
Situation: Quick lookup (email, phone, exists?)
Trigger phrases: "what's X's email", "find X", "do we have X"
Required action: Search only.
find_person("John Smith")
Situation: Full profile ("tell me about X", "what do you know about X")
Required action: Search, details, and notes.
Step 1: find_person("Sarah") -> get person_id
Step 2: get_person_details(person_id)
Step 3: get_notes(person_id)
Notes contain interaction history. Always include when user wants the full picture.
Situation: User wants to act on a person (note, reminder, update)
Required action: Search first, then act with the exact ID from the result.
Step 1: find_person("Sarah") -> get per_xxxxxxxx-xxxx-... ID from matches
Step 2: add_note(person_id=<exact ID from step 1>, content="...")
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 137 lines · 0 tokens per session scan A 9720e2ebcf76
mcp_folk is a skill published in the GitHub repository NimbleBrainInc/mcp-folk (6 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,072 tokens. 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.