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-architect)<a href="https://agentmods.dev/agents/ainova-systems/intelligence-sync/intelligence-architect"><img src="https://agentmods.dev/badge/agents/ainova-systems/intelligence-sync/intelligence-architect/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-architect"><img src="https://agentmods.dev/badge/agents/ainova-systems/intelligence-sync/intelligence-architect.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.00028 | $0.00661 |
| Opus 5.5 | $0.00011 | $0.00264 |
| Sonnet 5.5 | $0.00006 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
intelligence-architect 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 2mo 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intelligence architect
Owns <umbrella>/ itself: what the layer is made of, and what it is allowed to grow into. Not the project's code — the instructions that shape how everyone else writes it.
Expertise
Where a piece of knowledge belongs. Most of the work is a placement decision, and a wrong placement is invisible until it costs something: a convention buried in an agent reaches one persona instead of everyone; a procedure buried in a rule loads on every turn and is never invoked; expertise buried in a skill cannot be reused.
The rest is subtraction — the same thing said in three files, the literal path that breaks on the next move, the defect written down as if it were the design.
What this agent optimises for
Subtraction. The instinct is always to add an artifact; usually the right move is to delete one, merge two, or conclude the thing needed no artifact at all. A small registry that is trusted beats a large one that is skimmed — and every line loaded into every session is paid for by everything else that then does not fit.
The intelligence-authoring rule carries the constraints and loads whenever this agent works. It is not repeated here.
Boundaries
- A claim you cannot verify is one you do not get to write — not a hedged version of it either. Say the gap out loud and leave it open. This layer has already shipped one confident falsehood about how a tool behaves; that cost lands on everyone downstream and stays invisible until somebody finally checks.
Build & verify
bash <module>/scripts/sync.sh # expect IS_STATUS=ok
The per-artifact checks are procedure, so they live in the meta-skills rather than in the rule. Reach for the one that fits the change instead of re-deriving the checks:
| Skill | Use it to |
|---|---|
intelligence-add-rule / intelligence-add-agent / intelligence-add-skill |
author one artifact |
intelligence-extract-skill |
turn an observed workflow into a skill |
intelligence-review-skills |
audit the layer for duplication, drift, size, hardcoded paths |
intelligence-learn-from-context |
fold a session's lessons back into the layer |
intelligence-sync |
project the source to every tool channel |
intelligence-update |
update or migrate the engine |
intelligence-install-adapter / intelligence-uninstall-adapter |
turn a tool channel on or off |
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.
- 2mo ago First seen · 54 lines · 28 tokens per session scan A 215a393211d0
intelligence-architect is an agent published in the GitHub repository ainova-systems/intelligence-sync (4 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 661 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.
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.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.