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/altimateai/altimate-code/altimate-setupnpx skills add AltimateAI/altimate-code --skill altimate-setupgit clone --depth 1 https://github.com/AltimateAI/altimate-codeWhat 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.00016 | $0.00316 |
| Opus 5 | $0.00008 | $0.00158 |
| Sonnet 5 | $0.00003 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade D, and why
altimate-setup scanned grade D with 2 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 2d 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.
Harvests environment variableshighData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
2. **Gather credentials**: Ask the user for: Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
Then set permissions to owner-only: `chmod 600 ~/.altimate/altimate.json` What it actually says
Altimate Setup
Guide the user through configuring their Altimate platform credentials.
Steps
-
Check existing config: Read
~/.altimate/altimate.json. If it exists and is valid, show the current config (mask the API key) and ask if they want to update it. -
Gather credentials: Ask the user for:
- Altimate URL (default:
https://api.myaltimate.com) - Instance name (their tenant/org name, e.g.
megatenant) - API key (from Altimate platform settings)
- MCP server URL (optional, default:
https://mcpserver.getaltimate.com/sse)
- Altimate URL (default:
-
Write config: Create
~/.altimate/directory if needed, then write~/.altimate/altimate.json:{ "altimateUrl": "<url>", "altimateInstanceName": "<instance>", "altimateApiKey": "<key>", "mcpServerUrl": "<mcp-url>" }Then set permissions to owner-only:
chmod 600 ~/.altimate/altimate.json -
Validate: Call the
datamate_managertool withoperation: "list"to verify the credentials work. Report success or failure to the user.
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.
- 2d ago First seen · 32 lines · 16 tokens per session scan D f977d34942b1
altimate-setup is a skill published in the GitHub repository AltimateAI/altimate-code (803 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 316 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it D with 2 findings (harvests environment variables, asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
review-prs
Review a GitHub pull request in the googleapis/mcp-toolbox repo against the team's reviewer checklist: PR title/description conventions, linked issue, logic errors and unhandled edge cases, breaking changes, test coverage, docs updates, security (input handling), and new dependencies. Use whenever a maintainer asks…
fix-failing-tests
Diagnose a failing test in the googleapis/mcp-toolbox repo and land a fix by reasoning from the actual error: read the failure, reproduce it, shrink it until the cause is forced into the open, then fix the cause. Use this whenever a test or CI job is red, a build breaks after a change, many packages fail at once, or a…
stale-sweep
Sweep the googleapis/mcp-toolbox repo for issues and PRs with no real activity in N days (default 60), sort each by whose silence it is (the author's, ours, or nobody's), and draft the nudge or close comment. Use whenever a maintainer asks for a stale sweep, backlog cleanup, or an SLO check, e.g. "stale sweep", "find…
triage-issues
Triage GitHub issues in the googleapis/mcp-toolbox repo: propose the correct labels (type / priority / product / status), check for duplicates, verify a bug has enough info to act on, and draft a triage comment. Use whenever a maintainer asks you to triage, label, categorize, prioritize, or "look at" an issue (or a…
data-divergence
Investigate why two datasets that should agree don't — two pipelines writing the same logical table, a rollup vs the detail it aggregates, a dashboard vs its source, one environment vs another. Use when row counts, totals, or date ranges disagree and the question is what happened rather than just what differs. Covers…
sql-diagram
Diagram a SQL query and explain what it shows — either its execution steps (mode=plan) or its column lineage (mode=lineage) — then trace it through small data so the defects the picture cannot show become visible. Use when asked to visualize, diagram, explain or review what a query does, how it joins its tables, or…