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-add-agentnpx skills add ainova-systems/intelligence-sync --skill intelligence-add-agentgit 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.00009 | $0.01020 |
| Opus 5 | $0.00005 | $0.00510 |
| Sonnet 5 | $0.00002 | $0.00204 |
| Haiku 4.5 | $0.00001 | $0.00102 |
Grade A, and why
intelligence-add-agent 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Agent
Steps
-
Determine domain prefix (the scope is required):
- Reuse the existing domain when one fits: list
intelligence/agents/andintelligence/skills/. If a domain prefix is already established for the target area (backend-,frontend-,devops-), use it. Introduce a new domain only when the scope is materially different from all existing ones. - When no existing domain fits, derive from repo structure:
- Single / root project → use the project codename from
intelligence/config.yaml→project.name - Backend service / API component →
backend- - Frontend / web / UI component →
frontend- - Infrastructure, IaC, CI/CD, deployment →
devops- - Shared library / common / cross-cutting code →
core- - Test suites (e2e, integration) →
tests- - Tool-internal (intelligence-sync itself) →
intelligence-
- Single / root project → use the project codename from
- If the repo is a monorepo with named components (e.g.,
apps/billing,services/auth), prefer the component name as the domain (billing-,auth-). - Every agent needs a domain prefix. If the scope is unclear, ask the user before proceeding.
- Reuse the existing domain when one fits: list
-
Check existing agents: Read
intelligence/agents/to avoid duplicates. If an agent for this domain exists, ask user whether to update it instead. -
Determine tier and access:
- Developer agents:
tier: heavy,access: full - Reviewer/validator agents:
tier: standard,access: readonly - Simple lookup agents:
tier: light,access: readonly - Caveat:
readonly's closed tools list also removes MCP and tool-search access. A reviewer that needs MCP reads takesaccess: fullwith a read-only boundary stated in its body.
- Developer agents:
-
Analyze codebase: Read source files in the domain's directory to determine:
- Technology stack and frameworks
- Architecture patterns
- Build and test commands
- Key conventions and forbidden patterns
-
Create agent: Write
intelligence/agents/<domain>-<role>.mdwith frontmatter:--- name: <domain>-<role> description: "<when to use this agent - IDEs use this to suggest the agent>" tier: heavy|standard|light access: full|readonly skills: - <existing-skills-for-this-domain> ---
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 · 63 lines · 9 tokens per session scan A 1913195b2915
intelligence-add-agent is a skill published in the GitHub repository ainova-systems/intelligence-sync (4 stars, last pushed 4d ago), licensed MIT. It adds 9 tokens to every session and 1,020 once invoked, about $0.0000 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.