Borrowing it
Nothing to install: this file belongs to symphos-ai/orcho-core. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/symphos-ai/orcho-core/main/.agents/skills/orcho-core-verification-matrix/SKILL.mdgit clone --depth 1 https://github.com/symphos-ai/orcho-coreWrote 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/symphos-ai/orcho-core/orcho-core-verification-matrix)<a href="https://agentmods.dev/skills/symphos-ai/orcho-core/orcho-core-verification-matrix"><img src="https://agentmods.dev/badge/skills/symphos-ai/orcho-core/orcho-core-verification-matrix/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/symphos-ai/orcho-core/orcho-core-verification-matrix"><img src="https://agentmods.dev/badge/skills/symphos-ai/orcho-core/orcho-core-verification-matrix.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.00083 | $0.00598 |
| Opus 5.5 | $0.00033 | $0.00239 |
| Sonnet 5.5 | $0.00017 | $0.00120 |
| Haiku 4.5 | $0.00008 | $0.00060 |
Grade A, and why
orcho-core-verification-matrix 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orcho Core Verification Matrix
Map changed orcho-core surfaces to focused test commands before the full
integrity gate.
Owns
- targeted test and smoke selection for
orcho-core - pytest mark/path recommendations
- downstream smoke recommendations before final gate
Does Not Own
- implementation
- domain semantics
- final readiness gate ->
orcho-integrity-pipeline
First Reads
/Users/smartgamma/www/orcho/DEVELOPMENT_PIPELINE.mdorcho-core/AGENTS.md- changed source files
- nearest test directories
Test Map
| Changed surface | Start with |
|---|---|
| SDK schema/wire | orcho-core/tests/sdk/test_schema_snapshot.py, relevant tests/sdk/test_* |
| evidence slices/run diff | tests/sdk/test_evidence_slices.py, evidence tests, run diff tests |
| prompt boundary/cache | prompt tests under tests/unit/pipeline/prompts |
| runtime/session | runtime/session tests under tests/unit/pipeline |
| quality gates/parsers | parser and gate tests under tests/unit/pipeline |
| cross-project | tests/unit/pipeline/cross_project |
| CLI UX | tests/unit/cli |
| profiles/plugins | profile/plugin tests under tests/unit/pipeline |
| skills registry | tests/unit/pipeline/skills, skill parser tests |
| full mock behavior | relevant acceptance/integration mock flow |
Invariants
- Targeted tests do not replace final
ruff, pytest gate, andgit diff --check. - Public schema changes include snapshots and downstream smoke.
- Prompt golden diffs must be reviewed, not blindly accepted.
Verification
- This skill recommends commands; it does not replace running them.
- If public schema or MCP-visible shape changes, include snapshot and MCP smoke commands.
Output
Name primary domain skill, targeted commands, whether full pytest is still required, downstream smoke, and blockers if any command cannot run.
Command Policy
- Run commands from
orcho-coreunless the command explicitly names another repo. - Prefer
python -m pytest -q <path>for targeted tests. - Final readiness still belongs to
orcho-integrity-pipeline.
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 · 72 lines · 83 tokens per session scan A 48649659d6e1
orcho-core-verification-matrix is a skill published in the GitHub repository symphos-ai/orcho-core (5 stars, last pushed 17d ago), licensed Apache-2.0. It adds 83 tokens to every session and 598 once invoked, about $0.0003 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 skills, from other repositories
discount-review
Inspect the discount policy fixture with a repeatable review checklist and helper script.
code-review
Reviews code for bugs, security issues, and best practices.
quality-checklist
Validate implementation quality through custom checklists, scoring against constitution standards, specification coverage, and producing remediation recommendations.
orchestrated-execution
Execute work units through the rigorous 4-phase Metaswarm cycle (Implement -> Validate -> Adversarial Review -> Commit) with independent quality gate enforcement.
verification
Verification-before-completion discipline ensuring all success criteria are met, tests pass, and reviews complete before declaring work done.
ast-pe
An engineering delivery role for turning an approved design into working, tested, reviewable, and reversible software across modules. It covers implementation, integration, debugging, and delivery checks.