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 agentmods add skills/kyanitehq/linctl/checknpx skills add KyaniteHQ/linctl --skill checkgit 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.svg" alt="Measured on agentmods" 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 | $0.00052 | $0.00454 |
| Opus 5 | $0.00026 | $0.00227 |
| Sonnet 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 4d 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.
- 4d ago First seen · 30 lines · 52 tokens per session scan A 764d4746735c
check is a skill published in the GitHub repository KyaniteHQ/linctl (11 stars, last pushed 4d ago), licensed MIT. It adds 52 tokens to every session and 454 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.
Other skills, from other repositories
release-core-test
Invoke when dev-testing a Cyrus change that spans CYPACK (edgeworker + CLI) and CYHOST (Vercel-hosted GUI) and the hosted GUI needs to point at an unreleased cyrus-core from this repo. Publishes cyrus-core (and claude-runner if needed) as a -test.N prerelease under the npm test dist-tag so CYHOST can install it via…
cyrus-setup-claude-auth
Configure Claude Code authentication for Cyrus — API key, OAuth token, or third-party provider.
f1-test-drive
Orchestrate F1 test drives to validate the Cyrus agent system end-to-end across issue-tracker, EdgeWorker, and activity rendering.
verify-and-ship
Run all quality checks (tests, lint, typecheck), fix failures, update the changelog, commit, push, and create/update the pull request or merge request.
cyrus-setup-gitlab
Configure GitLab authentication for Cyrus — glab CLI login and git config for creating merge requests.
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.