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 vinnie357/claude-skills --skill altanagit clone --depth 1 https://github.com/vinnie357/claude-skillsWrote 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/vinnie357/claude-skills/altana)<a href="https://agentmods.dev/skills/vinnie357/claude-skills/altana"><img src="https://agentmods.dev/badge/skills/vinnie357/claude-skills/altana/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/vinnie357/claude-skills/altana"><img src="https://agentmods.dev/badge/skills/vinnie357/claude-skills/altana.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 21 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00082 | $0.01813 |
| Opus 5 | $0.00041 | $0.00907 |
| Sonnet 5 | $0.00016 | $0.00363 |
| Haiku 4.5 | $0.00008 | $0.00181 |
Grade A, and why
altana 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 7d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
altana skill
Procedural knowledge for working with the altana CLI — a tool that delegates prompts to named AI harness presets, collects structured JSON results, and fans out tasks across multiple harnesses for diverse-perspective synthesis.
Config Discovery
altana resolves its config in this order:
$ALTANA_CONFIG— if set, this path is used.~/.config/altana/altana.toml— default location.
Copy harnesses.example.toml from the altana repo root to get started:
mkdir -p ~/.config/altana
cp harnesses.example.toml ~/.config/altana/altana.toml
Full schema details in references/config.md.
Subcommands
delegate
altana delegate <harness> "<task>" [--prompt <template>] [--write]
Sends one task to one harness. Exits 0 on done, 1 on all other statuses.
Stdout: JSON object {harness, status, duration_s, log_path, response}.
Use --write only when the task requires the agent to modify files (awman executor only). council rejects --write presets.
council
altana council "<task>" [--harnesses a,b,c] [--rounds N] [--interactive] [--prompt <template>]
Fans the same task out to N harnesses in parallel (read-only). Returns a JSON array in config-declaration order.
One-shot mode (default): each array element has the same schema as delegate output — a single response string per harness. This is the default when --interactive is not supplied.
Interactive mode (--interactive): opens one persistent session per harness and runs R rounds (controlled by --rounds, default 2). From round 2 on, each harness sees labeled digests of its peers' prior-round answers and can react. Each result element carries a rounds array of {round, response} objects instead of a single response. Synthesis remains the caller's responsibility in both modes.
Interactive members require a ready_marker field in their harness config so altana knows when a turn is complete. See references/config.md for details.
Flags must appear after the task string: altana council "<task>" --interactive --rounds 1 --harnesses a,b.
What ships with it
2 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.
- 7d ago First seen · 183 lines · 82 tokens per session scan A c2746867be21
altana is a skill published in the GitHub repository vinnie357/claude-skills (25 stars, last pushed yesterday), licensed MIT. It adds 82 tokens to every session and 1,813 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…