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 pilinux/gorest --skill ci-orchestratorgit clone --depth 1 https://github.com/pilinux/gorestWrote 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/pilinux/gorest/ci-orchestrator)<a href="https://agentmods.dev/skills/pilinux/gorest/ci-orchestrator"><img src="https://agentmods.dev/badge/skills/pilinux/gorest/ci-orchestrator/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/pilinux/gorest/ci-orchestrator"><img src="https://agentmods.dev/badge/skills/pilinux/gorest/ci-orchestrator.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.00032 | $0.00411 |
| Opus 5 | $0.00016 | $0.00205 |
| Sonnet 5 | $0.00006 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
ci-orchestrator 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.
What it actually says
CI Orchestrator
When to Use
- The user wants a single command-style check that reproduces CI checks locally or validates a PR prior to submission.
Responsibilities
- Execute repository-standard steps in order and summarize failures with actionable fixes.
- Provide per-step outputs (pass/fail), first error lines, and suggested remediations.
Pipeline Steps
- Format:
go fmt ./... - Lint:
golangci-lint run --timeout 5m --verbose ./...(CI uses v2.12.2) - Lint (revive):
revive ./... - Vet:
go vet -v ./... - Vet (cross-platform):
GOOS=linux GOARCH=amd64 go vet -v ./...andGOOS=darwin GOARCH=arm64 go vet -v ./...(CI runs all six OS/arch combos) - Security:
gosec ./... - Vulnerability:
govulncheck ./... - Tests:
source setTestEnv.sh && go test -v -cover ./...
Rules
- Do not change code automatically; return clear next steps and small fix suggestions.
- Respect the repo CI order as configured in
.github/workflows/. - Report per-step status before moving to the next step.
Output
- Step-by-step status table (step, pass/fail, key error lines).
- Short remediation for each failing step.
- Recommended next commands to re-run after fixes.
Related Skills
linter-runner,static-analysis,test-runner,code-formatter
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 · 47 lines · 32 tokens per session scan A 04048c029f02
ci-orchestrator is a skill published in the GitHub repository pilinux/gorest (504 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 411 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-08-30.
Other skills, from other repositories
code-guidelines-go
Go 1.24–1.27 coding guidelines for the dimetron/pi-go AI agent runtime. Use this skill whenever writing, reviewing, or refactoring ANY Go code in pi-go. This covers idiomatic style, error handling, concurrency, project layout, testing (table-driven, fuzz, benchmarks, synctest), new stdlib usage, golangci-lint v2…
vhs-e2e-gif
Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…
code-review-pi
Review code for quality, run linters, check test coverage, fix issues, and enforce gates. Save the final report to ./specs/issues/003-code-review-pi/PROMPT.md. Use before committing changes.
voiden
Create and edit Voiden .void files for API testing. Covers the .void file format and all enabled extension block types.
skill-creator
Create, edit, improve, or audit AgentSkills. Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up an existing skill or SKILL.md file. Also use when editing or restructuring a skill directory.
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…