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 FrkAk/piyaz --skill onboardinggit clone --depth 1 https://github.com/FrkAk/piyazWrote 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/frkak/piyaz/onboarding)<a href="https://agentmods.dev/skills/frkak/piyaz/onboarding"><img src="https://agentmods.dev/badge/skills/frkak/piyaz/onboarding/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/frkak/piyaz/onboarding"><img src="https://agentmods.dev/badge/skills/frkak/piyaz/onboarding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00120 | $0.08594 |
| Opus 5.5 | $0.00048 | $0.03438 |
| Sonnet 5.5 | $0.00024 | $0.01719 |
| Haiku 4.5 | $0.00012 | $0.00859 |
Grade A, and why
onboarding 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 1mo 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 1mo ago First seen · 549 lines · 120 tokens per session scan A bfd7685bdbb4
onboarding is a skill published in the GitHub repository FrkAk/piyaz (196 stars, last pushed yesterday), licensed AGPL-3.0. It adds 120 tokens to every session and 8,594 once invoked, about $0.0005 per session on Opus 5.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
backlog
Use when the user asks to "review backlog", "analyze backlog quality", "backlog health", or invokes /compass-rose:backlog. Reads all open and wontfix issue files and analyzes quality via the backlog-analyzer agent.
reprioritize
Use when the user asks to "reprioritize", "update priorities", "scan codebase for relevance", or invokes /compass-rose:reprioritize. Scans codebase against local issue files and updates their priority/status meta tags.
add-item
Use when the user says "file an issue", "log this", "track this", "add a bug", "create a task", "add to backlog", or invokes /compass-rose:add-item. Replaces /lore-development:file-issue. Creates a local issue file in .lore/work/issues/.
migrate
Preview and, after explicit user confirmation, migrate pre-work and .lore/work lore layouts into historical intents, shared work, and gitignored local paths, converting legacy HTML artifacts to Markdown with original-byte backups. Does not migrate project files automatically.
init-rpm
Project setup and verification. First run creates rpm context for a project. Repeat runs verify that an existing rpm setup matches the latest expected layout and apply safe migrations.
backlog
Manage the rpm backlog (long-term project tasks in docs/rpm/future/tasks.org — distinct from Claude's native TaskCreate list, which is session-scoped). Add, list, review, postpone, or complete entries. TRIGGER on natural-language backlog operations — phrasings like "backlog X", "add X to backlog", "add to backlog"…