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 production-readinessgit 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/production-readiness)<a href="https://agentmods.dev/skills/elevanaltd/hestai-mcp/production-readiness"><img src="https://agentmods.dev/badge/skills/elevanaltd/hestai-mcp/production-readiness/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/production-readiness"><img src="https://agentmods.dev/badge/skills/elevanaltd/hestai-mcp/production-readiness.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.00401 |
| Opus 5 | $0.00000 | $0.00200 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
production-readiness 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
===SKILL:PRODUCTION_READINESS=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Production readiness validation and domain accountability for critical systems"
§1::VALIDATION_FRAMEWORK CRITICAL_LENSES::WILL_IT_BREAK×WILL_IT_SCALE×WHO_MAINTAINS×WHAT_ATTACKS×WHY_COMPLEX WILL_IT_BREAK::[single_points_of_failure, edge_cases, race_conditions] WILL_IT_SCALE::[10x_load_capacity, bottleneck_identification, resource_limits] WHO_MAINTAINS::[3am_debuggability, documentation, operational_runbooks] WHAT_ATTACKS::[attack_surface, vulnerability_assessment, defense_depth] WHY_COMPLEX::[justify_abstractions, simplification_opportunities]
§2::DOMAIN_ACCOUNTABILITY DOMAINS::[ AUTH_DOMAIN::[jwt_strategy, session_management, oauth_flows], SECRETS_MANAGEMENT::[vault_integration, rotation_policies], DEPLOYMENT_PIPELINE::[ci_cd_configuration, rollout_strategies], PERFORMANCE_MONITORING::[metrics_collection, alerting_thresholds], SECURITY_SCANNING::[vulnerability_assessment, dependency_audit], COMPLIANCE_VALIDATION::[regulatory_requirements, audit_trails], ARCHITECTURE_DECISIONS::[pattern_selection, scaling_strategies], TEST_INFRASTRUCTURE::[framework_selection, coverage_requirements] ]
§3::ARTIFACT_REQUIREMENTS MANDATORY_EVIDENCE::[ "System scales to 10x load"→"Load test report showing 10x capacity", "Zero-downtime deployment"→"Canary deployment logs + rollback test", "Security hardened"→"Penetration test report + OWASP compliance", "Production ready"→"Monitoring setup + runbook + incident response" ]
===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 · 36 lines · 0 tokens per session scan A b01a8a8f84d7
production-readiness 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 401 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
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.
atmos-sbom
Atmos SBOM provenance: CycloneDX and SPDX generation from vendor and Terraform evidence, coverage diagnostics, NTIA validation, and native CI workflow-artifact publication.
atmos-version
Atmos Version Tracker: version tracks, lock files, managed external dependency versions, atmos version track commands, !version, file managers, update policy, pinning, and CI verification.
atmos-cache
Atmos caching: CI cache configuration and commands, GitHub Actions cache integration, Terraform registry cache mirror/list/prune/stats/trust, and cache modernization guidance.