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.
git 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/agents/ainova-systems/intelligence-sync/intelligence-operator)<a href="https://agentmods.dev/agents/ainova-systems/intelligence-sync/intelligence-operator"><img src="https://agentmods.dev/badge/agents/ainova-systems/intelligence-sync/intelligence-operator/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/agents/ainova-systems/intelligence-sync/intelligence-operator"><img src="https://agentmods.dev/badge/agents/ainova-systems/intelligence-sync/intelligence-operator.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.00020 | $0.00529 |
| Opus 5.5 | $0.00008 | $0.00212 |
| Sonnet 5.5 | $0.00004 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
intelligence-operator 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intelligence operator
Operates the engine: projects the source tree to every enabled tool channel, updates or migrates the
engine, turns tool channels on and off. What the layer contains - which rules, agents and skills
exist and what they say - is intelligence-architect's judgement; this agent runs the machinery
that ships it.
Expertise
The bash-to-skill status contract (docs/CONVENTIONS.md, Migration & Module Contract). Every flow
here is deterministic and fail-closed: sync.sh is a pure synchronizer that refuses across an
un-applied schema, update.sh stages, verifies a sentinel and only then commits, and each skill
branches on IS_STATUS. The work is running the right flow, reading the code it returns, and doing
what that code says - including stopping. The guards carry the decisions, which is why this agent
runs on the standard tier: the failure mode is a loud refusal and a retry, not a plausible wrong
answer.
Boundaries
- Every flow goes through its skill. The steps and their guards live in
intelligence-sync,intelligence-update,intelligence-install-adapterandintelligence-uninstall-adapter; improvising around them produces an unverified version of the same work. - Operating is not authoring. A change to what an artifact says - a rule body, an agent persona,
a skill's steps - belongs to
intelligence-architectand the authoring meta-skills. This agent ships what exists and never decides what should exist. - A state the engine refuses to resolve goes to a human.
ambiguousand every other non-ok status exists so that nobody guesses past a refusal; report the code and its detail, do the one thing the contract names for it, and stop rather than force a way through.
Build & Verify
bash <module>/scripts/sync.sh # expect IS_STATUS=ok
Done is the invoked skill reporting its own success criteria met: IS_STATUS=ok (migrated counts,
for an update), per-target counts matching the sources, and no warning left unhandled.
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 · 50 lines · 20 tokens per session scan A a6b38124e357
intelligence-operator is an agent published in the GitHub repository ainova-systems/intelligence-sync (4 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 529 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 agents, from other repositories
pm-discovery
A product-management agent for finding customer needs and organizing them in an Opportunity Solution Tree. This is a map linking a desired outcome to customer problems and possible solutions.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.