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 Insajin/autopus-adk --skill auto-gogit clone --depth 1 https://github.com/Insajin/autopus-adkWrote 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/insajin/autopus-adk/auto-go)<a href="https://agentmods.dev/skills/insajin/autopus-adk/auto-go"><img src="https://agentmods.dev/badge/skills/insajin/autopus-adk/auto-go/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/insajin/autopus-adk/auto-go"><img src="https://agentmods.dev/badge/skills/insajin/autopus-adk/auto-go.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 Agent Snooping · line 41 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00015 | $0.07705 |
| Opus 5 | $0.00008 | $0.03853 |
| Sonnet 5 | $0.00003 | $0.01541 |
| Haiku 4.5 | $0.00002 | $0.00771 |
Grade A, and why
auto-go 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 10d 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 — 569 lines — stays where its author put it; the contents beside it link to each section on GitHub.
auto-go — SPEC 구현 스킬
OMP Invocation
/auto go .../auto-go ...- Load detail skill
auto-gofor either entrypoint.
OMP Team and Provider Axes
--teamselects ownerompnativetaskbatch with explicit Lead/Builder/Guardian responsibilities.--multiselects provider-diverse planning and review, not team execution topology.--team --multicomposes team execution with provider-diverse planning and review.- without
--teamor--solo, ownerompuses the default nativetaskbatch pipeline. --teamconflicts with--soloand ownerorca.- Lead, Builder, and Guardian coordinate only through native
task,hub, andtodo; the main OMP session owns the checklist and DAG.
Execution Owner Control Plane
- Invocation:
/auto go SPEC-ID [--execution-owner omp|orca]. Omission selectsompwith receipt sourcedefault; a supplied exact value has sourceexplicit. - Parse the flag exactly once before any
task, DAG-owningtodo, OMP subprocess, or Orca Run effect. Reject repeated, mixed, case-shifted, whitespace-padded, or aliased values without fallback. - Persist the body-free receipt
.autopus/pipeline-state/<SPEC-ID>.execution-owner.jsonwith schemapipeline_execution_owner_receipt.v1and only owner, source, reason, SPEC/run identity,checked_at, andverification_statusevidence. - Owner
omp: the current OMP session is the sole DAG owner, uses nativetask,hub, andtodo, and must not create an Orca Run. - Owner
orca: do not initialize an OMP task/todo DAG or calltask. Run and readorca skills get orchestration --full, then use its supervised durable cross-worktree Run contract. - At
auto pipeline run SPEC-ID --platform omp --execution-owner orca, the tier integrity gate runs and the receipt is persisted before any Run, worker, or provider session exists, and the pipeline then executes its phases on supervised Orca workers. Never retry a failure as owneromp.
프로젝트: autopus-adk | 모드: full
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.
- 10d ago First seen · 569 lines · 15 tokens per session scan A bf11357c2afd
auto-go is a skill published in the GitHub repository Insajin/autopus-adk (111 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 7,705 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
automations
Create, inspect, edit, archive, delete, run, and search scheduled or executable automation assets.
job
Execution behavior for one saved automation job running in a fresh agent conversation.
api-interface-design
Use when designing public APIs, module boundaries, provider adapters, tool schemas, or data contracts.
Using OmniForge Framework
Primary guide for using OmniForge CLI, MCP Server, workflows, and agent skills effectively.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
windows-deployment
Deploy FastAPI + React/Vite apps to Windows Server with NSSM services, reverse proxy (IIS or nginx), and git-pull workflow. Use when deploying any web app to a Windows prod server, setting up NSSM services, configuring IIS or nginx reverse proxy, making code environment-aware for dev/prod, or troubleshooting prod…