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/marcus/nightshift/nightshift-releasenpx skills add marcus/nightshift --skill nightshift-releasegit clone --depth 1 https://github.com/marcus/nightshiftWhat 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.00077 | $0.00766 |
| Opus 5 | $0.00039 | $0.00383 |
| Sonnet 5 | $0.00015 | $0.00153 |
| Haiku 4.5 | $0.00008 | $0.00077 |
Grade C, and why
nightshift-release scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
Clean up after: `rm -rf dist/`. How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Nightshift
Cut, publish, and verify releases for the nightshift Go project using goreleaser.
Pre-flight
- Ensure working tree is clean (
git status). - Determine the next version by checking
git tag --sort=-v:refname | head -1and asking the user what kind of bump (major/minor/patch) if not specified. - Confirm goreleaser is installed locally:
goreleaser --version. If missing, prompt user tobrew install goreleaser.
Release Workflow
1. Bump version in source
Edit cmd/nightshift/commands/root.go — update the Version variable to the new version (without the v prefix):
Version = "X.Y.Z"
2. Validate goreleaser config
Run a local dry-run to catch config errors before pushing:
goreleaser check
goreleaser release --snapshot --clean
checkvalidates.goreleaser.ymlsyntax.--snapshot --cleanbuilds all artifacts locally without publishing. Inspect thedist/directory to confirm binaries were produced for all expected OS/arch combos (darwin/amd64, darwin/arm64, linux/amd64, linux/arm64).
Clean up after: rm -rf dist/.
3. Commit, tag, and push
git add cmd/nightshift/commands/root.go
git commit -m "Bump version to vX.Y.Z"
git tag vX.Y.Z
git push origin main
git push origin vX.Y.Z
The v-prefixed tag triggers the GitHub Actions release workflow (.github/workflows/release.yml).
4. Verify release
After pushing the tag, verify the release pipeline succeeded:
# Watch the Actions run (blocks until complete)
gh run list --workflow=release.yml --limit 1
gh run watch # watch the most recent run
# Once complete, confirm the release exists
gh release view vX.Y.Z
Check that:
- The GitHub Actions run completed successfully.
- The release on GitHub lists all expected artifacts (tar.gz for each OS/arch + checksums.txt).
- The changelog was auto-generated and excludes docs/test/ci/chore commits.
If the homebrew cask was configured, also verify gh api repos/marcus/homebrew-tap/contents/Casks/nightshift.rb returns the updated cask.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 80 lines · 77 tokens per session scan C d670b0119313
nightshift-release is a skill published in the GitHub repository marcus/nightshift (1,011 stars, last pushed 1mo ago), licensed MIT. It adds 77 tokens to every session and 766 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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-check
检查发布版本号是否在三处保持一致(conf/conf.go、CHANGELOG.md、README.md)。在准备发布新版本时使用。.
add-goreleaser-homebrew
Add GoReleaser configuration and a GitHub Actions release workflow to an existing Go CLI project with Homebrew tap publishing. Use when the user says "add goreleaser", "set up goreleaser", "add Homebrew tap publishing", "publish to Homebrew", "set up release workflow", "add release automation for Go", or wants a Go…
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
greptimedb-release
Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…