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 Dianel555/DSkills --skill wiki-yylogit clone --depth 1 https://github.com/Dianel555/DSkillsWrote 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/dianel555/dskills/wiki-yylo)<a href="https://agentmods.dev/skills/dianel555/dskills/wiki-yylo"><img src="https://agentmods.dev/badge/skills/dianel555/dskills/wiki-yylo/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/dianel555/dskills/wiki-yylo"><img src="https://agentmods.dev/badge/skills/dianel555/dskills/wiki-yylo.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.00036 | $0.00972 |
| Opus 5.5 | $0.00014 | $0.00389 |
| Sonnet 5.5 | $0.00007 | $0.00194 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
wiki-yylo 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 today.
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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use YYLO wiki Records
Treat Ledger as the source of truth. Use yy ledger in a YYLO controller and
yylo-ledger in a standalone Ledger project. Inspect COMMAND wiki --help before
acting; if wiki is absent, the installed Ledger version does not expose native
Record commands and must not be bypassed with direct file edits.
Choose the right record
Before writing, decide where the information belongs:
- Wiki: durable explanatory project or domain knowledge that future work must discover.
- Task: scoped requested work, status, dependencies, acceptance criteria, and completion evidence.
- Workflow: validated structured steps, not prose guidance.
- Artifact: generated evidence, reports, receipts, logs, model output, or binary payloads.
- Source documentation: documentation released and versioned with product code.
Do not put secrets, caches, session transcripts, temporary status, bulky generated evidence, or owner-only operational receipts in a wiki.
Discover before creating
When an ID is known, preflight yy ledger get --help and prefer
yy ledger get RECORD_ID -f json without needing its type. If installed get is
task-only, use yy ledger record get RECORD_ID -f json after checking native help;
stop for an upgrade if unavailable. New generated wiki IDs use doc_; existing
IDs remain unchanged. Exact reads include hot and archived Records in the selected
project; never guess another type or project after a miss or ambiguity.
When no ID is known, use bounded summary searches first (use record search for
unknown kinds). Slugs and aliases are discovery conveniences, not replacement
identity. Universal get includes readable UTF-8 text up to 64 KiB by default;
inspect omission reasons instead of treating missing content as an empty page.
Use explicit --content --max-content-bytes N when needed (maximum 16 MiB).
Typed wiki get remains available for specialized source/rendering operations.
yy ledger wiki search --text "deployment policy" --projection summary --limit 20 -f json
yy ledger get RECORD_ID -f json
yy ledger wiki get RECORD_ID --raw
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 101 lines · 36 tokens per session scan A 3781bd84c4ca
wiki-yylo is a skill published in the GitHub repository Dianel555/DSkills (65 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 972 once invoked, about $0.0001 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-10-28.
Other skills, from other repositories
meeting-notes
Estructura y formatea notas de reunión siguiendo las mejores prácticas de PM. Úsalo cuando te pidan crear notas de reunión, formatear notas de discusión, capturar elementos de acción, o documentar decisiones de cualquier tipo de reunión. Produce notas estructuradas con decisiones, elementos de acción (responsable +…
technical-debt-register
Documenta y prioriza un backlog de deuda técnica con impacto empresarial, estimaciones de esfuerzo y estrategia de resolución. Úsalo cuando se te pida auditar deuda técnica, crear un registro de deuda, priorizar deuda técnica para un trimestre, documentar atajos arquitectónicos o construir una hoja de ruta de…
cs-health-scorecard
Construir un cuadro de mando de salud del cliente para una cuenta específica. Úsalo cuando te pidan calificar la salud de la cuenta, evaluar el riesgo de renovación, construir un panel de salud o evaluar la probabilidad de que una cuenta se renueve o expanda. Produce un cuadro de mando de salud estructurado con estado…
incident-postmortem
Escribe un postmortem de incidente estructurado o revisión post-incidente. Úsalo cuando se te pida escribir un postmortem, reporte de incidente, revisión P1/P2, reporte de apagón o RCA (análisis de causa raíz). Produce un postmortem sin culpables con cronología, causa raíz, factores contribuyentes, resumen de impacto…
stakeholder-update
Crear actualizaciones ejecutivas concisas para stakeholders usando el framework BLUF (Bottom Line Up Front). Usa cuando te pidan escribir una actualización de estado, reporte de progreso, comunicación de proyecto o briefing ejecutivo para liderazgo o stakeholders. Produce una actualización encabezada por BLUF con…
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…