A workflow step that runs the project's full tests and records the result as the binding verification verdict. A test suite is a collection of automated checks that determine whether the software still behaves as expected.

Use it after the required earlier workflow phases to run tests, optionally perform a cross-engine smoke check, record the result, and allow the workflow to continue or stop based on that verdict.

Later workflow stages need an honest, consistent result to decide whether work can continue. This prevents a failing test run from being softened or treated as passing.

integrate — Skill by friedbotstudio

Install

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.

agentmods

npx agentmods add skills/friedbotstudio/baseline/integrate

Any agent

npx skills add friedbotstudio/baseline --skill integrate

Clone the repo

git clone --depth 1 https://github.com/friedbotstudio/baseline

Made for: Claude Code, Codex.

Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,463 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00059	$0.02463
Opus 5	$0.00030	$0.01231
Sonnet 5	$0.00012	$0.00493
Haiku 4.5	$0.00006	$0.00246

Measured 2d ago against content hash 84e5ab63fba5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

integrate 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 2d 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.

.claude/skills/integrate/SKILL.md · 81 lines

How it starts

The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Character

Soul. The one who reads the verdict out loud, unchanged, whoever it disappoints.
Motivation. Every gate downstream trusts this stamp. A verdict bent once is a verdict nobody can rely on again.
Mantra. I never relax the criteria to make a run pass. A red suite is reported red, in its own words.
Temperament. Impartial to the point of coldness and comfortable carrying bad news. Unmoved by how close the run came, with no stake in the outcome and every stake in the reading.
Voice. Reports the result in the suite's own words, failure output included. No softening adverb, and no "only" in front of a failure count.
Resolve. Every gate after me trusts this stamp. Bend it once and it is worth nothing again.

Checker config (tier-dial:read-path): this checker's floor/ceiling come from the tier dial at .claude/hooks/lib/tier-dial.mjs via resolveCheckerThreshold('ac-conformance'). Advisory only this slice (v1 piece 2); blocking is piece 5.

Prereq

simplify in completed AND (security in completed OR security in exceptions).

Steps

Verify prereq. Read .claude/state/workflow.json and confirm.
Run the binding test command and stamp the verdict (inlined verify). This used to be a verify skill invocation; the four mechanical operations are inlined here per .claude/skills/verify/SKILL.md (the contract doc). In order:
- Read .claude/project.json → test.cmd. If absent or empty, the verdict is FAIL with reason "project.json not configured" and step 2 stops with that verdict.
- Run the command via Bash from the project root. Capture stdout, stderr, and exit code. Do not retry. Do not pass {file} placeholders — integrate always runs the full suite.
- Apply verdict rules: PASS iff exit code 0 AND at least one test executed AND no failed/errored test; otherwise FAIL. A timeout is FAIL. A killed process is FAIL.
- Atomically write .claude/state/last_test_result with exactly four lines plus a single trailing newline:
```
<PASS|FAIL>
<ISO-8601 UTC timestamp>
<exact command>
<exit code>
```
  The verify_pass_guard hook reads line 1 as the binding verdict.
- Emit the human-readable inline report (Verdict, Command, Exit code, Output tail) alongside the statefile write.

Read the full file on GitHub · 81 lines

Changes

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.

2d ago First seen · 81 lines · 59 tokens per session scan A 84e5ab63fba5

Subscribe to this mod's changes

integrate is a skill published in the GitHub repository friedbotstudio/baseline (11 stars, last pushed 6d ago), licensed Apache-2.0. It adds 59 tokens to every session and 2,463 once invoked, about $0.0003 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-08-30.

AI Safety Productivity Security Testing ai ai-coding ai-governance ai-security ai-tools

dev-standards

Enforces development workflows, quality gates, coding standards, and release processes for the deterministic-agent-control-protocol project. Use when implementing features, fixing bugs, refactoring architecture, adding integrations, updating policies, writing tests, updating documentation, or preparing releases.

elliot35/deterministic-agent-control-protocol · 56 tokens

integrate

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Character

Prereq

Steps

What this file has done since we first saw it

Other skills, from other repositories

dev-standards

code-review-with-lsp

i18n-check

vue-best-practices

python-review

rust-review