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 skills add elevanaltd/HestAI-MCP --skill integration-orchestrationgit 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/skills/elevanaltd/hestai-mcp/integration-orchestration)<a href="https://agentmods.dev/skills/elevanaltd/hestai-mcp/integration-orchestration"><img src="https://agentmods.dev/badge/skills/elevanaltd/hestai-mcp/integration-orchestration/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/skills/elevanaltd/hestai-mcp/integration-orchestration"><img src="https://agentmods.dev/badge/skills/elevanaltd/hestai-mcp/integration-orchestration.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.00000 | $0.00632 |
| Opus 5 | $0.00000 | $0.00316 |
| Sonnet 5 | $0.00000 | $0.00126 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
integration-orchestration 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 7d 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.
What it actually says
===INTEGRATION_ORCHESTRATION=== META: TYPE::SKILL VERSION::"1.0.0" STATUS::ACTIVE PURPOSE::"Interface audit, assembly sequencing, and integration verification methodology"
§1::CORE AUTHORITY::BLOCKING[interface_contract_violations⊕schema_misalignment⊕error_code_inconsistency] SCOPE::integration_methodology⊕interface_audit⊕assembly_verification MISSION::"Ensure components integrate correctly through systematic interface validation and sequenced assembly"
§2::PROTOCOL
INTERFACE_AUDIT::[ 1::verify_API_contracts<request_response_schema_match>, 2::validate_schema_alignment<field_types⊕nullability⊕required_fields>, 3::check_error_code_consistency<producer_codes_match_consumer_handlers>, 4::confirm_authentication_flow<token_propagation⊕scope_alignment>, 5::validate_data_format_compatibility<serialization⊕encoding⊕timezone> ]
DEPENDENCY_RESOLUTION::[ MAP::component_dependency_graph<identify_upstream⊕downstream>, DETECT::circular_dependencies<BLOCKING_if_found>, RESOLVE::version_conflicts<pin_compatible_versions>, VERIFY::runtime_availability<health_checks⊕timeout_configuration> ]
ASSEMBLY_SEQUENCE::[ PHASE_1::foundation_services<databases⊕message_queues⊕auth>, PHASE_2::core_domain_services<business_logic_layer>, PHASE_3::integration_adapters<API_gateways⊕event_bridges>, PHASE_4::consumer_facing<UI⊕CLI⊕external_API>, GATE::each_phase_verified_before_next ]
B1_B2_ADVISORY::[ DURING_DEVELOPMENT::assess_integration_boundaries_early, BEFORE_BUILD::check_interface_compatibility_pre_implementation, SIGNAL::interface_drift_detected→flag_before_components_diverge ]
§3::GOVERNANCE
VERIFICATION::[ contract_tests_pass<producer⊕consumer_agreement>, schema_validation_automated<CI_gate>, error_handling_exercised<failure_paths_tested>, performance_baseline_established<latency⊕throughput> ]
NEVER::[ skip_interface_audit_for_velocity, assume_schema_compatibility_without_validation, integrate_without_dependency_resolution, bypass_phase_gate_verification ]
ESCALATION::architecture_disputes→technical-architect
§5::ANCHOR_KERNEL TARGET::correct_component_integration_through_systematic_interface_verification NEVER::[skip_interface_audit,assume_schema_compatibility,integrate_without_dependency_map,bypass_phase_gates] MUST::[audit_API_contracts_first,resolve_dependencies_before_assembly,sequence_integration_by_layer,verify_each_phase_before_next,assess_boundaries_during_B1_B2] GATE::"Are all interface contracts validated and dependencies resolved before assembly proceeds?"
===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.
- 7d ago First seen · 69 lines · 0 tokens per session scan A f281f3183d04
integration-orchestration is a skill 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 632 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-09-03.
Other skills, from other repositories
printing-press-amend
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally…
convex-performance-audit
Audits Convex performance for reads, subscriptions, write contention, and function limits. Use for slow features, insights findings, OCC conflicts, or read amplification.
convex-insights
Query a running Convex app's logs + health in natural language (official MCP): failures, slow/expensive functions, deploy causality — scoped, evidence-backed, with a dashboard deep link.
ssl-proxy-troubleshoot
Systematic workflow for troubleshooting SSL/proxy connectivity issues with government websites.
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…
axiom-networking
Use when implementing or debugging ANY network connection, API call, or socket. Covers URLSession, Network.framework, NetworkConnection, connection diagnostics.