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 zcaudate-xyz/foundation-base --skill xtbench-triangulategit clone --depth 1 https://github.com/zcaudate-xyz/foundation-baseWrote 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/zcaudate-xyz/foundation-base/xtbench-triangulate)<a href="https://agentmods.dev/skills/zcaudate-xyz/foundation-base/xtbench-triangulate"><img src="https://agentmods.dev/badge/skills/zcaudate-xyz/foundation-base/xtbench-triangulate/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/zcaudate-xyz/foundation-base/xtbench-triangulate"><img src="https://agentmods.dev/badge/skills/zcaudate-xyz/foundation-base/xtbench-triangulate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00046 | $0.01326 |
| Opus 5 | $0.00023 | $0.00663 |
| Sonnet 5 | $0.00009 | $0.00265 |
| Haiku 4.5 | $0.00005 | $0.00133 |
Grade A, and why
xtbench-triangulate 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 10d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
xtbench Error Triangulation
Use this skill when an xtbench CI run is failing and you need to decide whether to look at the original xt.* test/implementation or at a language-specific spec/rewrite.
What it does
Given a GitHub Actions run URL (or run id), it:
- Downloads the run logs with
gh. - Parses the per-language failing-function summary that
lein seedgen testprints. - Maps generated
xtbench.<lang>.xt.*namespaces back to their originalxt.*source namespaces. - Groups failures by source namespace across languages.
- Reports:
- Shared source namespaces (failing in 2+ languages) → likely an issue in the original
test-lang/xt/...test orsrc-lang/xt/...implementation. - Language-specific namespaces (failing in only one language) → likely an issue in that language's spec/rewrite (
src/hara/model/spec_<lang>.clj,src/hara/model/spec_<lang>/rewrite.clj).
- Shared source namespaces (failing in 2+ languages) → likely an issue in the original
Prerequisites
ghCLI installed and authenticated (gh auth status).- Run inside the foundation-base repo root.
- The run must be for the
Run xtbench Testsworkflow (.github/workflows/run-xtbench.yml).
Quick usage
From a run URL
lein exec scripts/xtbench_triangulate.clj https://github.com/zcaudate-xyz/foundation-base/actions/runs/28731393184
From a bare run id
lein exec scripts/xtbench_triangulate.clj 28731393184
From an already-downloaded log directory
If you have already extracted the zip of logs:
lein exec scripts/xtbench_triangulate.clj /path/to/extracted-logs
Override the repo
lein exec scripts/xtbench_triangulate.clj 28731393184 --repo my-org/foundation-base
Manual workflow (no helper)
If you cannot use the helper script, do it by hand:
- Get the run id from the URL (
.../runs/<id>). - Download logs:
gh api repos/zcaudate-xyz/foundation-base/actions/runs/<id>/logs \ --method GET -H "Accept: application/vnd.github+json" > logs.zip unzip logs.zip -d xtbench-logs - Find the top-level job logs: files like
0_04 - xt.db _ dart.txt,11_01 - xt.lang _ lua.txt. - Extract the seedgen summary: look for the line
[seedgen] per-language failing functions:followed by a Clojure map. - Map back to source namespaces:
- Function symbols like
xt.lang.common-repl/notify-with-promise→ source nsxt.lang.common-repl. - Errored namespaces like
xtbench.dart.db.system.impl-sqlite-test→ source nsxt.db.system.impl-sqlite-test.
- Function symbols like
- Triangulate: same source ns in multiple languages → original xt.* issue; unique to one language → language spec/rewrite.
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.
- 10d ago First seen · 127 lines · 46 tokens per session scan A d19edc6d7f08
xtbench-triangulate is a skill published in the GitHub repository zcaudate-xyz/foundation-base (42 stars, last pushed 6d ago), licensed MIT. It adds 46 tokens to every session and 1,326 once invoked, about $0.0002 per session on Opus 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-02.
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.
smoke-test
Health smoke tests + auto-fix for gbrain installs (and OpenClaw services when present). Run after machine/container restarts or whenever something seems broken. Tests critical services, auto-fixes bounded local issues, and reports worker topology without starting daemons. Extensible via user-defined test scripts in…
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
debug-task
Diagnose and fix moon tasks that are broken, misconfigured, or behaving unexpectedly. Use this skill when a moon task is failing, not running, skipped, hanging, producing stale or wrong output, cached when it shouldn't be, re-running every time when it should be cached, or when outputs are empty or missing after a…
operating-github-ci-fixer
Use when the user asks OpenSRE to fix failing GitHub CI, GitHub Actions checks, failing pull request checks, a broken PR branch, or CI on a named branch such as main.
ci-triage
Classify CI failures — distinguish clear regressions from infra flakes and security-test failures. Produces structured failure reports.