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 takocode-chimera/takocode-mcp --skill get-startedgit clone --depth 1 https://github.com/takocode-chimera/takocode-mcpWrote 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/takocode-chimera/takocode-mcp/get-started)<a href="https://agentmods.dev/skills/takocode-chimera/takocode-mcp/get-started"><img src="https://agentmods.dev/badge/skills/takocode-chimera/takocode-mcp/get-started/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/takocode-chimera/takocode-mcp/get-started"><img src="https://agentmods.dev/badge/skills/takocode-chimera/takocode-mcp/get-started.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.00033 | $0.00480 |
| Opus 5.5 | $0.00013 | $0.00192 |
| Sonnet 5.5 | $0.00007 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
takocode-get-started 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 4d 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.
What it actually says
Get started with TakoCode
TakoCode's coding agent builds, hosts and publishes complete web apps on the user's TakoCode account. You are the orchestrator; TakoCode does the coding.
Setup steps
- Call
takocode_get_started. It reports whether the account is ready (membership, wallet balance, concurrency) and whether preferences are set. - If preferences are not set yet, ask the user these four questions in one
message and wait for the answers:
- Autonomy —
guided(confirm each costly step),auto_build(build freely, confirm publishing), orfull_auto(only stop for approvals the platform requires). - Questions — should TakoCode's agent
ask_userwhen a design or product decision comes up, oragent_decidesand note its assumptions? - Quality tier —
fast(quick, cheaper) orpro(stronger model). - Monthly budget — an optional hard spend cap in US dollars, or none.
- Autonomy —
- Save the answers with
set_preferencesand confirm what was saved. - If
takocode_get_startedreports that building is not available with the account's current membership or wallet balance, say so plainly and point the user to their TakoCode account (plans are described at https://takocode.com/pricing). Do not offer to buy anything — this plugin cannot purchase credits, memberships or domains. - Offer a first build: ask what the user wants to make, then follow the
build loop (
create_project→start_turn→ pollcheck_turnevery 20–30 seconds → share the preview link).
Rules
- Never invent prices and never claim that something has been paid.
publish_sitereports a monthly cost first; call it again withconfirm:trueonly after the user approves.- Everything built lives in the user's TakoCode account at https://takocode.com, where they can keep working on it directly.
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.
- 4d ago First seen · 41 lines · 33 tokens per session scan A 266b5bf0c897
takocode-get-started is a skill published in the GitHub repository takocode-chimera/takocode-mcp (0 stars, last pushed 5d ago), licensed MIT. It adds 33 tokens to every session and 480 once invoked, about $0.0001 per session on Opus 5.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-10-17.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…