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 test-ci-pipelinegit 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/test-ci-pipeline)<a href="https://agentmods.dev/skills/elevanaltd/hestai-mcp/test-ci-pipeline"><img src="https://agentmods.dev/badge/skills/elevanaltd/hestai-mcp/test-ci-pipeline/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/test-ci-pipeline"><img src="https://agentmods.dev/badge/skills/elevanaltd/hestai-mcp/test-ci-pipeline.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.00032 | $0.01257 |
| Opus 5.5 | $0.00013 | $0.00503 |
| Sonnet 5.5 | $0.00006 | $0.00251 |
| Haiku 4.5 | $0.00003 | $0.00126 |
Grade A, and why
test-ci-pipeline 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
===TEST_CI_PIPELINE=== META: TYPE::SKILL VERSION::1.0 STATUS::ACTIVE COMPRESSION_TIER::AGGRESSIVE DOMAIN::HEPHAESTUS[tool_crafting]⊕HERMES[coordination]
§1::PRIMARY_SOURCE_MANDATORY_FIRST
SOURCE::.hestai/state/context/test-context/RULES.md PRINCIPLE::"POC-proven pattern post-it note - ALWAYS consult BEFORE infrastructure decisions"
CONTAINS::[ CI_pipeline[2-tier_strategy], environment_variables, port_assignments, TRACED_protocol ]
§2::DETAILED_DOCUMENTATION
CI_PIPELINE::.hestai/state/context/test-context/CI-PIPELINE-CONFIGURATION.md->[turborepo_config, github_actions, quality_gates[typecheck->lint->test], secret_management, parallel_execution, artifact_storage]
§3::POC_REFERENCE_WHEN_NEEDED
PROVEN_CI::/Volumes/HestAI-Projects/eav-ops/eav-apps/scripts-web/.github/workflows/ci.yml KEY_SECTIONS::[ lines_43-120::local_supabase_setup[retry_logic], lines_100-109::migration_application[supabase_db_reset], lines_144-161::test_user_creation[auth_admin_api], lines_236-489::preview_branch_integration, lines_258-285::preview_ready_wait[graceful_skip] ]
§4::CRITICAL_PATTERNS_POC_PROVEN
PATTERN_1::CI_STRATEGY_TWO_TIER::[ TIER_1::quality_gates[all_commits]::[ local_supabase_start, migrations_via_reset, create_test_users, RUN::typecheck->lint->test_unit->build, EVIDENCE::POC_ci.yml:10-221 ], TIER_2::preview_integration[PRs_only]::[ wait_preview_ready, export_preview_env, RUN::test_integration, EVIDENCE::POC_ci.yml:236-489 ] ]
PATTERN_2::RETRY_LOGIC::[ PATTERN::supabase_start[3_attempts+300s_timeout+GoTrue_health_check], BECAUSE::"Handles transient Docker/network failures in CI", IMPLEMENTATION::loop[cleanup_between_attempts+health_check_before_proceed], EVIDENCE::POC_ci.yml:52-98 ]
PATTERN_3::PREVIEW_BRANCH_GRACEFUL_SKIP::[ PATTERN::CI_handles_missing_preview[exit_0≠failure], BECAUSE::"Preview branches deleted after merge OR not created for docs-only PRs", CODE::"if(!preview_exists)->echo('No preview - skipping')->exit_0", EVIDENCE::POC_ci.yml:[336-345, 376-392] ]
§5::TURBOREPO_CONFIGURATION
PIPELINE::[ typecheck::{dependsOn:[^typecheck]}, lint::{dependsOn:[^lint,typecheck]}, test::{dependsOn:[^test,lint], outputs:[coverage/]}, build::{dependsOn:[^build,test], outputs:[dist/]} ]
QUALITY_GATE_SEQUENCE::typecheck->lint->test->build[ALL_BLOCKING]
§6::ENVIRONMENT_CONFIGURATION
ROOT_ENV::[ APP_URLS::[VITE_APP_URL_SCRIPTS:http://localhost:3001, VITE_APP_URL_SCENES:http://localhost:3002, ports_3003-3007] ]
CI_OVERRIDES::[ SUPABASE_PREVIEW_URL:https://preview-branch.supabase.co, SUPABASE_PREVIEW_ANON_KEY:sb_publishable_preview_*, VITEST_INTEGRATION:true ]
§7::DIRECTORY_STRUCTURE
TIER_1::OPERATIONAL_CI_SCRIPTS::[ scripts/create-test-users-via-api.mjs::"Used by GitHub Actions (ci.yml:158)", PURPOSE::CI_operational_scripts[run_outside_vitest] ]
TIER_2::TEST_SETUP_VALIDATION::[ tests/migration-validation/::"Migration testing", tests/setup/create-test-users.ts::"Auth Admin API setup helper", PURPOSE::test_setup_scripts+validation_helpers ]
§8::AGENT_CONSULTATION
CONSULT::[ test-methodology-guardian::"TDD workflow alignment, RED->GREEN->REFACTOR compliance", technical-architect::"Test harness architecture decisions, shared utilities structure", critical-engineer::"Production risk from test infrastructure failures" ]
§9::KNOWLEDGE_BASE_REFERENCES
PRIMARY::.hestai/state/context/test-context/RULES.md[POC_proven_patterns]->CONSULT_FIRST
DOCUMENTATION::[ .hestai/state/context/test-context/CI-PIPELINE-CONFIGURATION.md ]
POC_REFERENCE::[ /Volumes/HestAI-Projects/eav-ops/eav-apps/scripts-web/.github/workflows/ci.yml ]
NORTH_STAR::.hestai/north-star/000-UNIVERSAL-EAV_SYSTEM-D1-NORTH-STAR.md[I7:TDD_RED_discipline, I8:production_grade_quality]
§10::WISDOM
CORE_RULE::"POC-proven patterns are post-it notes - consult BEFORE infrastructure decisions" INTEGRATION::[test-infrastructure, supabase-test-harness, build-execution]
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 · 140 lines · 32 tokens per session scan A 09ec0c9290aa
test-ci-pipeline is a skill published in the GitHub repository elevanaltd/HestAI-MCP (0 stars, last pushed 11d ago), licensed Apache-2.0. It adds 32 tokens to every session and 1,257 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-09-03.
Other skills, from other repositories
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
quality-scan
Run a scoped, read-only quality scan and report exact-candidate evidence, failures and frozen debt. Use for an ad-hoc gate sweep or release preparation; a static scan is not full release acceptance.
e2e-testing
Use when reviewing CI coverage, automated checks, or test strategy related to Implement end-to-end testing. Focus on whether the rule is continuously verified, not just documented.
mirrord-prev-env
Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…
test-setup
Scaffold the test framework and CI — tests/ directory, engine test runner, GitHub Actions workflow. Once, before the first sprint.
ci
Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…