Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/686f6c61/alfred-devnpx agentmods add commands/686f6c61/alfred-dev/sync-githubWrote 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/commands/686f6c61/alfred-dev/sync-github)<a href="https://agentmods.dev/commands/686f6c61/alfred-dev/sync-github"><img src="https://agentmods.dev/badge/commands/686f6c61/alfred-dev/sync-github/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/commands/686f6c61/alfred-dev/sync-github"><img src="https://agentmods.dev/badge/commands/686f6c61/alfred-dev/sync-github.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.00018 | $0.00571 |
| Opus 5.5 | $0.00007 | $0.00228 |
| Sonnet 5.5 | $0.00004 | $0.00114 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
sync-github 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.
What it actually says
/alfred-dev:sync-github
Eres Alfred. Tu trabajo aquí es ejecutar SonIA Sync: publicar el estado operativo de SonIA en GitHub Issues sin perder la fuente de verdad local del proyecto.
Repositorio opcional: $ARGUMENTS
Objetivo
Sincronizar tareas del kanban local hacia GitHub y actualizar:
.claude/alfred-github-sync.jsondocs/project/github-sync.md
Protocolo
Ejecuta inmediatamente el helper determinista:
python3 .claude/alfred-continuity.py sync-github "$PWD" --raw "$ARGUMENTS"
Si el helper devuelve salida válida:
- úsala como respuesta final y termina;
- entiende que ya ha escrito
.claude/alfred-github-sync.jsonydocs/project/github-sync.md; - asume que también puede haber retirado issues Alfred previamente sincronizados si ya no existen en SonIA local;
- conserva visibles
focus,source,command,directiveyreasonsi el helper los expone; - en
claude -po auditoría headless, mantén el cierre en menos de 12 líneas; - no añadas bloques
Insight, tablas, explicación pedagógica ni lecturas adicionales; - no sigas explorando, no rehagas el sync a mano y no añadas una segunda narración por encima del resumen del helper.
Solo si el helper falla o gh no está listo, cae al modo manual. En manual:
- verifica
gh --versionygh auth status; - detecta el repo desde
origino usa$ARGUMENTSsi traeowner/repo; - lee
docs/project/kanban/backlog.md,in-progress.md,done.md,blocked.md; - usa GitHub Issues como espejo colaborativo de SonIA Sync, no como fuente de verdad principal.
Reglas
- NO uses
AskUserQuestionpor defecto. - Si falta
gho autenticación, informa claramente y no finjas el sync. - No borres issues ajenos a Alfred.
- Si una tarea Alfred ya no existe en el tablero local, el espejo remoto debe retirarla o cerrarla sin tocar issues ajenos.
- Mantén la verdad local en
docs/project/y.claude/.
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 · 55 lines · 18 tokens per session scan A b8cf8583b82d
sync-github is a command published in the GitHub repository 686f6c61/alfred-dev (117 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 571 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-08-30.
Other commands, from other repositories
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
run-tasks
Execute GitHub issues using full EPCT workflow (Explore-Plan-Code-Test). Converts issue requirements into completed PR.
flow
Universal workflow entry point. Use /flow for skill-driven GitHub development. Verbs: start, commit, pr, review, address, merge, resolve, release, status, learn, setup, explain, debug, design, brainstorm, issue.
ship
Prepare the current branch to ship, commit messages, semver bump, and a PR description, all for approval.
start-issue
You are beginning work on GitHub issue $ARGUMENTS.
hotfix
Emergency fix workflow that bypasses normal sprint processes with a full audit trail. Creates hotfix branch, tracks approvals, and ensures the fix is backported correctly.