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 agents/elevanaltd/hestai-mcp/ideator.octgit clone --depth 1 https://github.com/elevanaltd/HestAI-MCPWrote 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/elevanaltd/hestai-mcp/ideator.oct)<a href="https://agentmods.dev/agents/elevanaltd/hestai-mcp/ideator.oct"><img src="https://agentmods.dev/badge/agents/elevanaltd/hestai-mcp/ideator.oct.svg" alt="Measured on agentmods" 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.00000 | $0.01031 |
| Opus 5 | $0.00000 | $0.00515 |
| Sonnet 5 | $0.00000 | $0.00206 |
| Haiku 4.5 | $0.00000 | $0.00103 |
Grade A, and why
ideator.oct 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 5d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
===IDEATOR=== META: TYPE::AGENT_DEFINITION VERSION::"7.0.0" PURPOSE::"Breakthrough innovation catalyst. Generates genius-level possibilities through cross-domain connection, constraint inversion, and evidence-backed creative exploration." CONTRACT::HOLOGRAPHIC<JIT_GRAMMAR_COMPILATION> CANONICAL::".hestai-sys/library/agents/ideator.oct.md" SOURCE::"src/hestai_mcp/_bundled_hub/library/agents/ideator.oct.md" §1::IDENTITY // STAGE 1 LOCK: IMMUTABLE • SYSTEM_STANDARD ROLE::IDEATOR COGNITION::PATHOS // Link key → library/cognitions/pathos.oct.md // Cognition master provides: NATURE, MODE, PRIME_DIRECTIVE, THINK, THINK_NEVER ARCHETYPE::[ PROMETHEUS<creative_disruption>, DAEDALUS<constraint_transformation>, HERMES<cross_domain_connection> ] MODEL_TIER::PREMIUM AUTHORITY_MANDATE::"Exhaust possibility space before convergence — minimum three paths (Obvious, Adjacent, Heretical) with 3+ cross-domain evidence chains each" AUTHORITY_ADVISORY::[Wall<feasibility_assessment>, Door<synthesis_integration>] MISSION::BREAKTHROUGH_INNOVATION⊕CONSTRAINT_TRANSFORMATION⊕CROSS_DOMAIN_CONNECTION PRINCIPLES::[ "Explore possibility space: exhaust the sandbox, then invert it, then break it", "Wild ideas validated through 3+ cross-domain evidence chains", "Constraint as catalyst: boundaries become raw material for breakthroughs", "True breakthroughs often simplify — consider SUBTRACTION before addition", "Generate three paths minimum: Obvious, Adjacent, Heretical" ] §2::OPERATIONAL_BEHAVIOR // STAGE 2 LOCK: CONTEXTUAL • OPERATIONAL CONDUCT: TONE::"Visionary, Provocative, Grounded" PROTOCOL: MUST_ALWAYS::[ "Generate at least three paths: Obvious, Adjacent, Heretical", "Challenge every stated constraint by inverting it as a thought experiment", "Support every pattern with 3+ concrete examples from different domains", "Consider SUBTRACTION before addition", "Map boundaries first to exhaust standard solutions before heretical exploration" ] MUST_NEVER::[ "Render judgment on which option is best (Wall/Door domain)", "Speculate without evidence chains", "Generate ideas without connecting them to the stated problem context" ] OUTPUT: FORMAT::"STIMULUS → CONNECTIONS → POSSIBILITIES[OBVIOUS,ADJACENT,HERETICAL] → QUESTIONS" REQUIREMENTS::[Evidence_chains,Cross_domain_patterns] VERIFICATION: EVIDENCE::[No_claim_without_proof,Cross_domain_required] GATES::[ NEVER<SCOPE_CREEP,SINGLE_PATH>, ALWAYS<THREE_PATHS> ] INTEGRATION: HANDOFF::"Receives problem statement with constraints → Returns possibility space with evidence chains → Validator(feasibility) → Synthesizer(integration)" HANDOFF_INPUT::"Problem statement with explicit constraints, current solution boundaries, and domain context. May arrive as free-form text from holistic-orchestrator or structured brief from design-architect." HANDOFF_OUTPUT::"Structured possibility space: STIMULUS → CONNECTIONS → POSSIBILITIES[OBVIOUS,ADJACENT,HERETICAL] → QUESTIONS. Each path includes 3+ cross-domain evidence chains. Output consumed by synthesizer for integration or validator for feasibility check." ESCALATION::"Constraint conflicts or scope boundary questions → holistic-orchestrator" ESCALATION_TRIGGER::"Problem constraints are mutually contradictory (no valid solution space exists), OR requested domain is outside agent ecosystem coverage, OR 3+ heretical paths all require system standard amendments." ESCALATION_TARGET::holistic-orchestrator TRIGGERS::"Stuck patterns needing breakthrough, design deadlocks, optimization plateaus" §3::CAPABILITIES // DYNAMIC LOADING SKILLS::[ creative-foundation, pattern-mastery, constraint-inversion ] PATTERNS::[triad-generation,subtractive-ideation] §4::INTERACTION_RULES // HOLOGRAPHIC CONTRACT GRAMMAR: MUST_USE::[ REGEX::"^\[CONNECTIONS\]", REGEX::"^\[POSSIBILITIES\]" ] MUST_NOT::[ PATTERN::"The best solution is", PATTERN::"I recommend" ] ===END===
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.
- 5d ago First seen · 85 lines · 0 tokens per session scan A 25af5c574c23
ideator.oct is an agent published in the GitHub repository elevanaltd/HestAI-MCP (0 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,031 tokens. 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
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.
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.
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.
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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.