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 Arvo-AI/aurora --skill spinnakergit clone --depth 1 https://github.com/Arvo-AI/auroraWrote 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/arvo-ai/aurora/spinnaker)<a href="https://agentmods.dev/skills/arvo-ai/aurora/spinnaker"><img src="https://agentmods.dev/badge/skills/arvo-ai/aurora/spinnaker.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00024 | $0.00567 |
| Opus 5 | $0.00012 | $0.00283 |
| Sonnet 5 | $0.00005 | $0.00113 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
spinnaker 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 8d 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
Spinnaker Integration
Overview
Spinnaker CD platform integration for investigating pipeline executions and application health during Root Cause Analysis. Use during RCA to check if deployments correlate with incidents.
Instructions
Tool: spinnaker_rca
Query Spinnaker CD platform for root cause analysis and interactive investigation.
Actions:
recent_pipelines-- List recent pipeline executions; optionalapplicationfilter andlimitpipeline_detail-- Get full execution with stage-by-stage status. Requiresexecution_idapplication_health-- Cluster + server group health. Requiresapplicationlist_pipeline_configs-- Available pipeline definitions. Requiresapplicationtrigger_pipeline-- Trigger a pipeline (e.g. rollback). Requiresapplication+pipeline_name, optionalparametersexecution_logs-- Detailed logs for failed stages. Requiresexecution_id
RCA Investigation Flow
spinnaker_rca(action='recent_pipelines', application='APP')-- Check for recent pipeline executionsspinnaker_rca(action='pipeline_detail', execution_id='ID')-- Get stage-by-stage status for a suspicious executionspinnaker_rca(action='application_health', application='APP')-- Check cluster and server group healthspinnaker_rca(action='execution_logs', execution_id='ID')-- Get detailed logs for failed stagesspinnaker_rca(action='list_pipeline_configs', application='APP')-- List available pipelines (e.g. to find a rollback pipeline)spinnaker_rca(action='trigger_pipeline', application='APP', pipeline_name='rollback')-- Trigger rollback if needed
Important Rules
- Check
recent_pipelinesfirst to correlate deployments with incident timing. - Use
pipeline_detailto get stage-by-stage breakdown before reading logs. - Use
application_healthto assess current cluster state. - Only use
trigger_pipeline(e.g. for rollback) after confirming root cause with 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.
- 8d ago First seen · 53 lines · 24 tokens per session scan A 837645f0973a
spinnaker is a skill published in the GitHub repository Arvo-AI/aurora (405 stars, last pushed yesterday), licensed Apache-2.0. It adds 24 tokens to every session and 567 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
tax-lawyer-software-interfaces
MCP tool design patterns for the Tax-Lawyer Platform. Thin Satisfies wrappers (<=10 lines per handler), TaxArgs contract types, and the full tool name taxonomy for ledgerrtax MCP actions.
b00t
Identify integration points, data flow via redis, suggest how to bridge VSCode plugin to b00t jobs, and outline k0s/podman/docker-agnostic redis interface. Include how ralph should be wrapped as b00t job with redis exchange + Azure access, and call out where integration tests are required. ONLY do this analysis. Reply…
isaac-automator
Deploy and operate a cloud Isaac Workstation with Isaac Automator: provision a GPU VM running Isaac Sim, Isaac Lab, and/or Isaac Lab Arena on AWS, GCP, Azure, or Alibaba Cloud, connect to it, move data in and out, control cost with stop/start, repair, import existing deployments, and destroy. Use when the user wants a…
cloud-iam-deep
GCP/AWS/Azure cloud exploitation -- Cloud Functions, Firestore, Cloud Run, S3, MinIO, Blob Storage, SA keys.
ak-add-integration
Add a messaging platform integration to an existing Agent Kernel project. This skill guides you through adding Slack, WhatsApp, Messenger, Instagram, Telegram, Teams, or Gmail integration by generating configuration, updating dependencies, and setting up webhook handlers. Designed for users extending their agents.
Cloud Security & Container Hardening
AWS/Azure/GCP security auditing, container and Kubernetes hardening, Infrastructure as Code scanning, and cloud compliance assessment.