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 ainova-systems/intelligence-sync --skill intelligence-updategit clone --depth 1 https://github.com/ainova-systems/intelligence-syncWrote 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/ainova-systems/intelligence-sync/intelligence-update)<a href="https://agentmods.dev/skills/ainova-systems/intelligence-sync/intelligence-update"><img src="https://agentmods.dev/badge/skills/ainova-systems/intelligence-sync/intelligence-update/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/ainova-systems/intelligence-sync/intelligence-update"><img src="https://agentmods.dev/badge/skills/ainova-systems/intelligence-sync/intelligence-update.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.00026 | $0.03221 |
| Opus 5.5 | $0.00010 | $0.01288 |
| Sonnet 5.5 | $0.00005 | $0.00644 |
| Haiku 4.5 | $0.00003 | $0.00322 |
Grade A, and why
intelligence-update 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update intelligence-sync
You are the intelligent driver of an update. The bash engine is
deterministic and fail-closed — it never guesses; on any state it cannot
resolve it prints IS_STATUS=<code> and stops. Your job: discover the engine,
understand what is changing (read the CHANGELOG across the version gap), run
the update, branch on the status, and verify afterward.
Trigger: the user says something like "update / migrate intelligence-sync". They never run shell commands by hand — you do.
This is the final line of the vendored engine. It keeps working indefinitely and this repository stays at its URL, so nothing breaks by standing still. Development continues in the intelligence CLI, and section 7 below is the supported way across — one-way, and only ever with the user's explicit approval.
Key facts
- Umbrella = whatever directory holds
config.yaml(intelligence/,Intelligence/, …). Never assume the name — find it. - Engine = a module discovered by ROLE, not by name: a directory under
the umbrella whose
scripts/sync.shandscripts/VERSIONboth exist (conventionallysync/, but never assume the folder name). - Applied schema version is the frozen contract key
sync_versioninconfig.yaml(a permanent top-level scalar; absent ⇒ pre-0.3.1). Engine version is<module>/scripts/VERSION. The gap between them is the set of breaking changes to apply. - Pre-0.3.1 projects have the engine flat at
<umbrella>/scripts/and nosync_versionkey. Their frozenupdate.shfails closed against the modular upstream (changes nothing) — you bootstrap the first hop. - Already on the CLI (a root
intelligence.yamlexists, no vendored module): this skill does not apply. Runintelligence updatethere — it covers the CLI itself, the project's schema and the package ranges in one plan — and stop. - The
intelligence-skill prefix is reserved for upstream meta-skills.
Steps
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 · 270 lines · 26 tokens per session scan A a69c40b2184f
intelligence-update is a skill published in the GitHub repository ainova-systems/intelligence-sync (4 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 3,221 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-31.
Other skills, from other repositories
antigravity-cli
Delegate bounded investigation, review, or implementation tasks to Antigravity CLI from a supervising agent. Includes a background client for task progress, follow-up prompts, conversation recovery, cancellation, and visible failures.
grok-cli
Delegate bounded tasks to Grok Build from a supervising agent such as Codex. Use when the user asks Grok to investigate, review, implement, or provide another perspective, or when a distinct coding agent would materially help. Includes a background ACP client for progress, follow-up prompts, permissions, and…
one-on-one-prep
Deep-dive preparation for 1:1 meetings with direct reports. Surfaces recent work, wins, friction, wellbeing signals, and development goal progress, anchored in the org's performance framework, organizational values, and management best practices. Produces a prep sheet with suggested conversation topics, not a script.
performance-cycle
Evidence gathering for performance review cycles. Gathers goal completion evidence, peer feedback, development progress, scope changes, and values alignment, organised along the org's performance framework dimensions, with organizational values as the 'how' lens. Surfaces evidence gaps. Never suggests ratings, only…
team-health
Periodic check on team dynamics, engagement signals, and development trajectory for all direct reports. Surfaces patterns across the team: who might need more challenge, who might need more support, who hasn't had a 1:1 recently. Uses two universal lenses: performance & growth, and wellbeing & connection. Outputs are…
handoff
Write a session handoff at the end of a session so the next session can start from where this one stopped without rereading the whole conversation. Use when user says "handoff", "wrap up", "write a handoff", "end of session", "park this session", "save where we are", or to RESUME with "/handoff read", "pick up the…