Borrowing it
Nothing to install: this file belongs to friedbotstudio/baseline. 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/friedbotstudio/baseline/main/.claude/skills/integrate/SKILL.mdgit clone --depth 1 https://github.com/friedbotstudio/baselineWrote 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/friedbotstudio/baseline/integrate)<a href="https://agentmods.dev/skills/friedbotstudio/baseline/integrate"><img src="https://agentmods.dev/badge/skills/friedbotstudio/baseline/integrate/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/friedbotstudio/baseline/integrate"><img src="https://agentmods.dev/badge/skills/friedbotstudio/baseline/integrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 68 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Agent Snooping · line 30 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00059 | $0.02463 |
| Opus 5.5 | $0.00024 | $0.00985 |
| Sonnet 5.5 | $0.00012 | $0.00493 |
| Haiku 4.5 | $0.00006 | $0.00246 |
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 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 — 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.mjsviaresolveCheckerThreshold('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.jsonand confirm. -
Run the binding test command and stamp the verdict (inlined verify). This used to be a
verifyskill 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 isFAILwith 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:
PASSiff exit code 0 AND at least one test executed AND no failed/errored test; otherwiseFAIL. A timeout is FAIL. A killed process is FAIL. - Atomically write
.claude/state/last_test_resultwith exactly four lines plus a single trailing newline:
The<PASS|FAIL> <ISO-8601 UTC timestamp> <exact command> <exit code>verify_pass_guardhook reads line 1 as the binding verdict. - Emit the human-readable inline report (Verdict, Command, Exit code, Output tail) alongside the statefile write.
- Read
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 · 81 lines · 59 tokens per session scan A 84e5ab63fba5
integrate is a skill published in the GitHub repository friedbotstudio/baseline (14 stars, last pushed 13d ago), licensed Apache-2.0. It adds 59 tokens to every session and 2,463 once invoked, about $0.0002 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-30.
Other skills, from other repositories
code-review-with-lsp
Code review with LSP-powered code intelligence. Uses MCP tools (diagnostics, hover, references, definition, symbols) for semantic code understanding, not just text grep.
i18n-check
An internationalization (i18n) check for software that supports multiple languages. It compares translation files with the text and translation keys used by the code.
vue-best-practices
A review checklist for Vue 2 and Vue 3 components, covering component names, prop declarations, TypeScript casts, API styles and complex template expressions.
gdpr-audit
GDPR compliance audit of code, plans, schemas, or IaC. Produces a findings report with article citations, severity, confidence, and fixes; flags evidence gaps. Not a substitute for a DPO/lawyer.
cognitive-walkthrough
Deep-dive usability evaluation of specific user tasks. Simulates novice user cognition step-by-step to identify learnability issues, unclear actions, and points of confusion.
owasp-ai-testing
AI trustworthiness testing using OWASP AI Testing Guide v1. Execute 32 test cases across 4 layers (Application, Model, Infrastructure, Data) with practical payloads and remediation.