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/Incept5/eve-skillpacksnpx agentmods add skills/incept5/eve-skillpacks/sync-horizonWrote 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/incept5/eve-skillpacks/sync-horizon)<a href="https://agentmods.dev/skills/incept5/eve-skillpacks/sync-horizon"><img src="https://agentmods.dev/badge/skills/incept5/eve-skillpacks/sync-horizon/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/incept5/eve-skillpacks/sync-horizon"><img src="https://agentmods.dev/badge/skills/incept5/eve-skillpacks/sync-horizon.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.00039 | $0.03818 |
| Opus 5 | $0.00019 | $0.01909 |
| Sonnet 5 | $0.00008 | $0.00764 |
| Haiku 4.5 | $0.00004 | $0.00382 |
Grade A, and why
sync-horizon 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 8d 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 — 380 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync Horizon
Synchronize eve-skillpacks with the latest state of the eve-horizon repository.
Core Insight
System docs often lag behind implementation. Features ship via feat commits with plans marked "Implemented" — but docs/system/ may not update for weeks. This sync goes to the source: plans, code changes, and commit messages tell us what actually shipped. System docs are one signal among many, not the primary driver.
Prerequisites
- The eve-horizon repo must be at
../eve-horizon(sibling directory) .sync-state.jsonmust exist in the repo root (create from template if missing).sync-map.jsonmust exist in the repo root
Architecture: Orchestrator + Parallel Workers
You (the orchestrator) discover what shipped and dispatch focused workers. Each worker handles one update in isolation with its own context budget.
The orchestrator reads lightweight signals (commit log, plan headers, file stats, CLI module list). Workers read the heavy content (plan bodies, code diffs, source docs, target files).
Output Standards
- Distill only shipped platform behavior. Plans marked Implemented/Complete describe shipped features.
- Do not carry roadmap content into skillpacks. Ignore plans marked Proposed/Draft and sections like
Planned (Not Implemented),What's next, or "current vs planned" framing. - Keep
eve-work/eve-read-eve-docs/SKILL.mdtask-first: route by intent, load only the minimal reference files needed. - Keep reference docs scoped and actionable — curated distillations, not copies.
Workflow
Phase 1: Deep Discovery (orchestrator)
Read lightweight signals from multiple dimensions to understand what actually shipped.
1a. Commit log
cd ../eve-horizon && git log --oneline <last_synced_commit>..HEAD
Categorize commits:
feat:— new capabilities (primary interest)fix:— bugfixes that may affect documented behaviordocs:— documentation changes (check if they describe already-shipped features)chore:/refactor:— usually no skillpack impact, but note removals
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.
- 8d ago First seen · 380 lines · 39 tokens per session scan A d10e9c031936
sync-horizon is a skill published in the GitHub repository Incept5/eve-skillpacks (0 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 3,818 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-31.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.