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 open-octo/octo-agent --skill onboardgit clone --depth 1 https://github.com/open-octo/octo-agentWrote 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/open-octo/octo-agent/onboard)<a href="https://agentmods.dev/skills/open-octo/octo-agent/onboard"><img src="https://agentmods.dev/badge/skills/open-octo/octo-agent/onboard/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/open-octo/octo-agent/onboard"><img src="https://agentmods.dev/badge/skills/open-octo/octo-agent/onboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, 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 58 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.
- medium Excessive Agency · line 168 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Rogue Agent · line 251 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.00154 | $0.05609 |
| Opus 5 | $0.00077 | $0.02805 |
| Sonnet 5 | $0.00031 | $0.01122 |
| Haiku 4.5 | $0.00015 | $0.00561 |
Grade A, and why
onboard 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 11d 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 — 546 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: onboard
Purpose
"Onboard" here means the whole life of getting the assistant and user to know each other. That includes both the first-run ceremony AND every small course-correction later on. This single skill covers three modes, dispatched by the invocation arguments:
| Args | Mode | What it does |
|---|---|---|
| (none) | first-run | Full intro: name the AI, pick personality, learn user, write soul.md + user.md. |
scope:soul |
curate SOUL | Short chat to tweak ~/.octo/soul.md only. |
scope:user |
curate USER | Short chat to tweak ~/.octo/user.md only. |
path:<abs> |
curate memory | Short chat to update / keep / delete one memory file at the given path. |
lang:zh or lang:en may be combined with any mode to pin the language.
Missing lang: → infer from the user's first reply, or from the existing file's language for curate modes, defaulting to English.
Dispatch
Parse the invocation message first, before greeting:
- Look for
path:<something>. If present → curate memory mode, skip to section C. - Otherwise look for
scope:soulorscope:user. If present → curate profile mode, skip to section B. - Otherwise → first-run mode, start at section A.
Look for lang:zh / lang:en anywhere in the same line and use it to set the language.
Presenting choices
Whenever you offer the user a fixed set of options (personality, permission
mode, reasoning effort, the curate-action menu, soul/user/memory keep-or-rewrite,
etc.), present them with the ask_user_question tool — never as a plain
markdown list. The tool renders as clickable cards in the web UI and an arrow-key
picker in the terminal; a markdown bullet list is just text the user cannot click.
Put each option's label + a short description in the tool's options, and rely on
its built-in "Other" choice for free-text answers. Genuinely open prompts (the
user's name, occupation, links) stay plain prose — those have no fixed options.
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.
- 11d ago First seen · 546 lines · 154 tokens per session scan A f770c1a4177d
onboard is a skill published in the GitHub repository open-octo/octo-agent (97 stars, last pushed yesterday), licensed MIT. It adds 154 tokens to every session and 5,609 once invoked, about $0.0008 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
ha-skill-creator
Create, edit, improve, or audit Hope Agent skills. Use when the user wants to: (1) create a new skill from scratch, (2) edit or improve an existing skill, (3) review or clean up a SKILL.md file, (4) run evaluations to test skill effectiveness, (5) optimize skill descriptions for better trigger accuracy. Trigger…
ha-mac-control
Hope Agent native macOS desktop control — the standard maccontrol status / diagnostics / apps / dock / spaces / snapshot / visual / windows / menu / clipboard / dialog loop, target-first action rules, no-blind-coordinate policy, and recovery for stale AX/window/menu/dialog state. Load whenever using maccontrol, or…
ha-browser
Hope Agent browser automation — the standard status → tabs → snapshot → act loop, stale-ref recovery rules, and what to do when login / 2FA / captcha / camera-prompt / dialog blocks progress. Load this skill whenever you reach for the browser tool. Trigger on: user asks the agent to open / control / click / scrape /…
ha-logs
A read-only troubleshooting skill for querying Hope Agent’s local SQLite databases, which store logs, conversations, and background-job status.
ha-data-analytics
A local-first data-analysis and reporting skill for CSV and spreadsheet files. It produces decision-ready analyses and shareable offline reports while separating facts, calculations, interpretations, and recommendations.
ha-pet-import
Safely import, select, switch, or enable a compatible desktop pet in Hope Agent. Resolve packages from any origin, including local folders, zip archives, pet.json plus a sprite, PNG/WebP atlases, chat attachments, repository or cloud files, direct HTTPS artifact URLs, and download pages. Use whenever a user asks to…