Borrowing it
Nothing to install: this file belongs to KyaniteHQ/linctl. 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/KyaniteHQ/linctl/master/.claude/skills/check/SKILL.mdgit clone --depth 1 https://github.com/KyaniteHQ/linctlWrote 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/kyanitehq/linctl/check)<a href="https://agentmods.dev/skills/kyanitehq/linctl/check"><img src="https://agentmods.dev/badge/skills/kyanitehq/linctl/check/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/kyanitehq/linctl/check"><img src="https://agentmods.dev/badge/skills/kyanitehq/linctl/check.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.00052 | $0.00454 |
| Opus 5.5 | $0.00021 | $0.00182 |
| Sonnet 5.5 | $0.00010 | $0.00091 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
check 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.
What it actually says
check — linctl pre-PR gate
Run the complete local gate for the linctl repo and report each step's result. go tool task ci and go tool task coverage are the gate; run them before any PR.
task is a pinned Go tool dependency — always invoke it as go tool task, never fetch an unpinned task binary at run time.
Run these in order, capturing pass/fail and key output for each. Do not stop at the first failure — run all, then report.
go tool task ci— deps-check, fmt-check, generate-check (generated client, command reference, upstream schema/coverage-ledger checks), domain-language-check, browser-login-smoke-check, vet, test, build, smoke-run, lint, shellcheck, actionlint, vuln.go tool task coverage(separate fromci) — enforces 100% hand-written statement coverage; generated.go, cmd/linctl/main.go, and scripts/ are excluded. Fails with the uncovered file:line.
The upstream schema/coverage-ledger checks in ci need network access to github.com/linear/linear unless a reusable checkout is already prepared. Use LINCTL_LINEAR_SDK_UPSTREAM=/path/to/linear to point at one, and LINCTL_LINEAR_SDK_OFFLINE=1 to skip the refresh fetch against it (fails loud if the checkout doesn't exist).
Do NOT run task live-smoke here — it needs a disposable Linear token and hits the live API. Mention it separately if the change touches transport/client behavior.
Report in this shape:
Gate results:
- ci: PASS
- coverage: FAIL — internal/cli/foo.go:42 uncovered
Fix failures at the root, re-run the failed gate, and only report green once every gate passes.
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 · 30 lines · 52 tokens per session scan A 764d4746735c
check is a skill published in the GitHub repository KyaniteHQ/linctl (12 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 454 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
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
golang-stretchr-testify
Comprehensive guide to stretchr/testify for Golang testing. Covers assert, require, mock, and suite packages in depth. Use when writing tests with testify, creating mocks, setting up test suites, or choosing between assert and require. Covers testify assertions, mock expectations, argument matchers, call verification…
go-127
What changed in Go 1.27 (released August 2026) and how it changes the way Go is written in pi-go. Use this skill when writing or reviewing Go that could use a 1.27 feature, when bumping the go directive in go.mod, when a build or test behaves differently after a toolchain upgrade, or when code-guidelines-go points…
bubbletea-testing
Use this skill whenever writing tests for Bubble Tea (charmbracelet/bubbletea) TUI applications in Go. Triggers include any mention of testing Bubble Tea models, teatest, golden file testing for TUIs, testing tea.Cmd or tea.Msg, snapshot testing terminal output, or writing tests for any Go CLI/TUI that uses the Elm…
check-linters-before-commit
Before any commit, run linters, vet, tests, and build verification; do not commit until checks pass.
write-tests
Writes a unit test for one Python function. Use when the user asks for tests of existing code; not for integration tests.