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 fabricioctelles/jump-skills --skill yylo-ninjagit clone --depth 1 https://github.com/fabricioctelles/jump-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/fabricioctelles/jump-skills/yylo-ninja)<a href="https://agentmods.dev/skills/fabricioctelles/jump-skills/yylo-ninja"><img src="https://agentmods.dev/badge/skills/fabricioctelles/jump-skills/yylo-ninja/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/fabricioctelles/jump-skills/yylo-ninja"><img src="https://agentmods.dev/badge/skills/fabricioctelles/jump-skills/yylo-ninja.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.00209 | $0.02123 |
| Opus 5.5 | $0.00084 | $0.00849 |
| Sonnet 5.5 | $0.00042 | $0.00425 |
| Haiku 4.5 | $0.00021 | $0.00212 |
Grade A, and why
yylo-ninja 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.
How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YYLO Ninja
Jump Skill — Master orchestrator that routes YYLO workflow tasks to 7 specialized skills from the official YYLO repository.
Purpose
This skill acts as an intelligent router to the canonical YYLO skills library. Instead of manually searching for the right skill, describe your workflow task and this skill will:
- Identify the most relevant specialized skill(s)
- Load the full skill instructions on demand
- Execute the task with expert-level YYLO knowledge
Prerequisites
The skills drive the yy CLI (npm package @yylo/cli, Node.js 20.10+ and Git). Before executing a task:
- Verify
yy --helpworks; if not, install withnpm install --global '@yylo/cli@latest' yy ledgerandyy benchmarkdelegate to the separately installedyylo-ledger/yylo-benchmarkCLIs — Record namespaces must appear in the installedyy ledger --helpbefore an agent uses them- The four Ledger Record skills (wiki, workflow, artifact, ledger-tasks) are usable with standalone Ledger; the planning and execution skills rely on YYLO orchestration
- Inspect
COMMAND --helpbefore acting; if a namespace is absent, the installed version does not expose it — do not fall back to editing Ledger storage directly
Read operations (listing tasks, searching wiki Records, inspecting artifacts) are safe to run directly. Mutating operations (finishing tasks, landing merges, creating Records) change repository state — confirm with the user first, and never push, deploy, or mutate production without separate authority.
Skill Catalog
Task Management
| Skill | Path | Use When |
|---|---|---|
ledger-tasks-yylo |
{{JUMP_SKILLS_DIR}}/repos/yylo-ninja/yylo-skills/skills/ledger-tasks-yylo/ |
Operate the YYLO Ledger board: create, list, search, mark, update, archive tasks, manage dependencies and ordering |
plan-ledger-tasks-yylo |
{{JUMP_SKILLS_DIR}}/repos/yylo-ninja/yylo-skills/skills/plan-ledger-tasks-yylo/ |
User explicitly asks to plan or register work: draft one concise PDR and create implementation-sized Ledger tasks |
understand-project-yylo |
{{JUMP_SKILLS_DIR}}/repos/yylo-ninja/yylo-skills/skills/understand-project-yylo/ |
Inspect product architecture, dependencies, and validation loops BEFORE planning or implementing a change |
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 · 181 lines · 209 tokens per session scan A 21d806e9b188
yylo-ninja is a skill published in the GitHub repository fabricioctelles/jump-skills (33 stars, last pushed 2d ago), licensed MIT. It adds 209 tokens to every session and 2,123 once invoked, about $0.0008 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-09-16.
Other skills, from other repositories
ovh
OVHcloud infrastructure integration for managing instances, Kubernetes clusters, networks, and object storage via CLI and Terraform.
scaleway
Scaleway cloud integration for managing instances, Kapsule Kubernetes clusters, object storage, and managed databases via CLI and Terraform.
ak-cloud-deploy
Deploy an Agent Kernel project to AWS, Azure, or GCP using Terraform modules, or to any Kubernetes cluster (on-prem, baremetal, EKS) using the official Helm chart. Supports serverless and containerized modes for all three clouds. AWS supports execution modes (restsync, restasync, async, stream), queue-based scalable…
cloudbees_oc
CloudBees Operations Center integration for cross-controller deployment visibility and feature flag correlation during RCA.
terrashark
Prevent Terraform/OpenTofu hallucinations by diagnosing and fixing failure modes: identity churn, secret exposure, blast-radius mistakes, CI drift, and compliance gate gaps. Use when generating, reviewing, refactoring, or migrating IaC and when building delivery/testing pipelines.
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…