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/ainova-systems/intelligence-sync/intelligence-updatenpx skills add ainova-systems/intelligence-sync --skill intelligence-updategit clone --depth 1 https://github.com/ainova-systems/intelligence-syncWhat 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.00026 | $0.03221 |
| Opus 5 | $0.00013 | $0.01611 |
| Sonnet 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 2d 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.
- 2d 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 4d ago), licensed MIT. It adds 26 tokens to every session and 3,221 once invoked, about $0.0001 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
ux-writing
Judgment rules for user-facing text and docs: CLI and diagnostic output, error and help text, README and docs structure, code comments, titles, and generated reports, decks, or exports. Use when writing or changing any user-visible string, when adding or restructuring docs or deciding which page owns a fact, when a…
talk-like-scarletkc
按 scarletkc 本人的自然表达习惯撰写、改写、润色和翻译文本，覆盖推文、微博、评论、聊天消息、技术观点、项目介绍、GitHub 文本（README、issue、PR、发布说明）和正式通信。当用户要求用自己的口吻写东西、把 AI 腔文字改自然、发推、回评论、点评模型或开发工具、写项目公告、写礼貌但直接的客服或正式邮件，或要求翻译时保留语气和立场，都使用本 skill，即使用户没有点名 scarletkc 或提出风格要求。.
marketing-copy
Write outbound promotional copy for a product or project: launch and update posts for community platforms and social media, store page descriptions and short blurbs, landing page headlines and calls to action, press-style announcements, and the naming of a product for another language or market. Covers what may be…
scoped-change
Judgment rules for locating the correct boundary of a requested change: staying inert outside it while completing every required site inside it. Use when scope is ambiguous, a diff touches neighboring surfaces, required dependent edits are unclear, or a proposed compatibility layer, migration, fallback, flag…
worktree-pr
Decide whether a task deserves its own git worktree and, if chosen, run it end to end: branch from the integration branch rather than the current tree, keep the main working copy untouched while the task runs, compare the result against the untouched baseline before declaring it done, and prepare it for a pull request…
agentic-code-review
Use when reviewing a diff, pull request, branch, or AI-generated code for correctness, security, regression, test, performance, and maintainability risks before merge.