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 agentmods add skills/686f6c61/alfred-dev/sync-project-docsnpx skills add 686f6c61/alfred-dev --skill sync-project-docsgit clone --depth 1 https://github.com/686f6c61/alfred-devWhat 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 | $0.00037 | $0.00412 |
| Opus 5 | $0.00018 | $0.00206 |
| Sonnet 5 | $0.00007 | $0.00082 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
sync-project-docs 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 3d 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.
What it actually says
Sincronizar documentación viva
Resumen
Tras una fase, actualiza solo lo que ha cambiado. El helper crea esqueletos y comprueba la gate. Tú escribes el contenido.
Proceso
-
Esqueleto e índice:
python3 .claude/alfred-continuity.py sync-project-docs "$PWD" -
Lee
docs/project/README.mdy el protocolocommands/_docs_vivas.md. -
Actualiza únicamente los ficheros de la fase. Si no hubo API nueva, no toques una guía de API. Si no hubo decisión, no inventes un ADR.
-
Cuando un esqueleto tenga contenido real, deja
<!-- alfred-doc:filled -->y quita<!-- alfred-doc:scaffold -->. -
Comprueba la gate:
python3 .claude/alfred-continuity.py check-project-docs "$PWD" --command <comando> --phase <fase> -
Si el helper falla, no declares la fase cerrada.
En quick y fix
Sync mínimo: índice + docs/project/current.md. ADR solo si el cambio mueve
un límite (auth, persistencia, integración).
Criterios de éxito
- El índice refleja el estado real (
scaffoldofilled). - No hay prosa inventada sobre código que no se ha tocado.
check-project-docssale 0 antes de cerrar la gate.
Qué NO hacer
- No reescribas todo
docs/en cada fase. - No copies el chat al Markdown.
- No marques
filledsi siguen los_(pendiente)_.
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.
- 3d ago First seen · 53 lines · 37 tokens per session scan A bd44ae0b8668
sync-project-docs is a skill published in the GitHub repository 686f6c61/alfred-dev (119 stars, last pushed 18d ago), licensed MIT. It adds 37 tokens to every session and 412 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.