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/getcargohq/cargo-skillsnpx agentmods add skills/getcargohq/cargo-skills/cargo-projectWrote 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/getcargohq/cargo-skills/cargo-project)<a href="https://agentmods.dev/skills/getcargohq/cargo-skills/cargo-project"><img src="https://agentmods.dev/badge/skills/getcargohq/cargo-skills/cargo-project/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/getcargohq/cargo-skills/cargo-project"><img src="https://agentmods.dev/badge/skills/getcargohq/cargo-skills/cargo-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
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.00218 | $0.05883 |
| Opus 5.5 | $0.00087 | $0.02353 |
| Sonnet 5.5 | $0.00044 | $0.01177 |
| Haiku 4.5 | $0.00022 | $0.00588 |
Grade A, and why
cargo-project 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 today.
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 — 358 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cargo project — a Cargo workspace, declared in a repo
Use this skill to define a Cargo workspace in TypeScript (define* builders from
@cargo-ai/cdk) and reconcile it to live infrastructure with cargo-ai project deploy.
It is the declarative counterpart to the imperative capability skills: instead
of running one CLI command per resource, you write the whole graph once and deploy
it repeatably, with a deploy state — held in your workspace, pointed at by a
committed cargo.state.json — linking your code to what Cargo created.
"Project" and "workspace" are two different things — keep them apart. A workspace is the Cargo tenant you sign into: it holds the models, connectors, agents, mailboxes and credits, and it is what
login --workspace-nameselects and whatwhoamireports. A project is the repo that declares resources and deploys them into a workspace: it is whatproject initscaffolds, whatcargo.state.jsonpoints from, and what--dirlocates. One project deploys into one workspace at a time — the workspace guard refuses a deploy when the state's workspace isn't the selected one — and the same project reaches a dev and a prod workspace through a different deploy state each. Say "project" for the repo, and don't name a project directorymy-workspace.
Bootstrap
Already signed in (cargo-ai whoami returns a workspace)? Skip to the next section.
npm install -g @cargo-ai/cli # no global install? prefix every command with `npx @cargo-ai/cli`
cargo-ai login --email [email protected] # emailed code, no browser; creates the account on first use
# alternatives: --oauth (browser) · --token <api-token> (CI)
cargo-ai whoami # confirm the active workspace before any write
cargo-ai project --help # `unknown command` = CLI too old; reinstall @cargo-ai/cli@latest
Two CDK-specific extras: the project needs @cargo-ai/cdk as a dependency for the define* builders you import (cargo-ai project init scaffolds a package.json with it — then npm install), and the cargo-ai project domain ships with the CLI itself.
What ships with it
14 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.
- guides/authoring-resources.md 13 KB
- guides/deploy-and-state.md 7.1 KB
- guides/typed-config.md 2.7 KB
- recipes/add-connector-and-model.md 2.2 KB
- recipes/build-an-agent.md 3.2 KB
- recipes/deploy-from-ci.md 2.8 KB
- recipes/migrate-existing-workspace.md 2.6 KB
- recipes/scaffold-a-project.md 3.0 KB
- references/commands.md 5.2 KB
- references/cookbooks.md 32 KB
- references/examples/full-workspace.md 4.4 KB
- references/resources.md 9.5 KB
- references/troubleshooting.md 4.8 KB
- skill-metadata.json 2.2 KB
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.
- today Changed · +2 lines 1b144e1b3ebe
- 8d ago Changed · +1 tokens per session 81fc775ab4d0
- 15d ago Changed · +2 lines 61d5b2b4d56d
- 1mo ago Changed · +68 lines 26d61bfedb19
- 1mo ago First seen · 286 lines · 217 tokens per session scan A 1cc781918f85
cargo-project is a skill published in the GitHub repository getcargohq/cargo-skills (19 stars, last pushed today), licensed MIT. It adds 218 tokens to every session and 5,883 once invoked, about $0.0009 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-09-15.
Other skills, from other repositories
everme-memory
Use EverMe cloud memory proactively when the user refers to previous conversations, earlier decisions, "last time", "remember when", existing project conventions, or previously solved errors, and save durable user preferences, habits, and decisions the moment they are stated. Do not repeat a search when the host…
memory-tools
Use EverMe memory proactively when the user refers to previous conversations, earlier decisions, "last time", "remember when", existing project conventions, or previously solved errors, and save durable user preferences, habits, and decisions the moment they are stated. Do not repeat a search when a non-empty block…
everme-agent-skill
Read the full body of an EverMe agent skill before doing the work it covers. Use when an injected block or an EverMe search result lists an agent skill (a [skill ] line with a name and a one-line summary) whose summary matches the task in hand. The summary is not the procedure; fetch the body once, then follow it.
memory-recall
Session-start primer that tells Kimi how EverMe's automatic cross-session memory works and how to treat the injected recall/profile context.
gtm-engineering
When the user wants to build GTM automation with code, design workflow architectures, use AI agents for GTM tasks, or implement the 'architecture over tools' principle. Also use when the user mentions 'GTM engineering,' 'GTM automation,' 'n8n,' 'Make,' 'Zapier,' 'workflow automation,' 'Clay API,' 'instruction stacks,'…
ai-cold-outreach
When the user wants to build an AI-powered outreach system, write cold emails, improve deliverability, or scale personalized outreach. Also use when the user mentions 'cold email,' 'cold outreach,' 'outreach automation,' 'Instantly,' 'Smartlead,' 'Clay,' 'email sequences,' 'deliverability,' 'personalization at scale,'…