Borrowing it
Nothing to install: this file belongs to loerei/chronicle-mcp. 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/loerei/chronicle-mcp/main/.agents/skills/set-up-package-scripts/SKILL.mdgit clone --depth 1 https://github.com/loerei/chronicle-mcpWrote 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/loerei/chronicle-mcp/set-up-package-scripts)<a href="https://agentmods.dev/skills/loerei/chronicle-mcp/set-up-package-scripts"><img src="https://agentmods.dev/badge/skills/loerei/chronicle-mcp/set-up-package-scripts.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.1 | $0.00024 | $0.01157 |
| Opus 5 | $0.00012 | $0.00579 |
| Sonnet 5 | $0.00005 | $0.00231 |
| Haiku 4.5 | $0.00002 | $0.00116 |
Grade A, and why
set-up-package-scripts 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 7d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set Up Package Scripts
Configure, harden, and structure npm/pnpm package scripts with fail-fast preflight gates, deterministic asset pipelines, and clean lifecycle boundaries.
Directives
- Fail-Fast Gating: Heavy build commands (
build,build:linux,build:win,release) MUST chain lightweight verification steps FIRST (verify:deps,typecheck,lint) before invoking heavy packagers or compilers. - Deterministic Script Hierarchy: Group package scripts using standard namespace prefixes (
build:*,test:*,verify:*,ensure:*,sync:*,clean:*). - Cross-Platform Resilience: Package scripts MUST run identically on Windows (cmd/PowerShell), macOS (zsh), Linux (bash), and CI/Docker environments without machine-specific absolute paths.
- Zero Silent Failures: Verification scripts MUST exit with code
1(process.exit(1)) on any unresolved dependency or assertion failure to immediately halt downstream build steps. - No Secret Mutation in CI: Verification commands (
verify:deps) MUST be read-only auditors. Auto-mutating tools (sync:deps,lint:fix,format) MUST be separated into dedicated commands.
Canonical Script Taxonomy
{
"scripts": {
"// PREFLIGHT & AUDITING": "",
"verify:deps": "node scripts/verify-packaged-dependencies.js",
"sync:deps": "node scripts/verify-packaged-dependencies.js --fix",
"typecheck": "tsc --noEmit",
"lint": "biome check src",
"lint:fix": "biome check --write src",
"check": "npm run verify:deps && npm run typecheck && npm run test",
"// COMPILATION & ASSETS": "",
"ensure:bins": "node scripts/ensure-binaries.js",
"copy:assets": "copyfiles -u 1 \"src/assets/**/*\" dist",
"build:preload": "tsup src/preload.ts --out-dir dist --format cjs --external electron",
"build:main": "tsc -p tsconfig.main.json",
"build:vite": "vite build",
"// PACKAGING & ARTIFACTS (FAIL-FAST)": "",
"organize:build-output": "node scripts/organize-build-output.js",
"build": "npm run check && npm run ensure:bins && npm run build:preload && npm run build:main && npm run copy:assets && npm run build:vite && electron-builder --win && npm run organize:build-output",
"build:linux": "npm run check && npm run ensure:bins && npm run build:preload && npm run build:main && npm run copy:assets && npm run build:vite && electron-builder --linux && npm run organize:build-output",
"build:fast": "npm run verify:deps && npm run build:preload && npm run build:main && npm run copy:assets && npm run build:vite && electron-builder --dir && npm run organize:build-output",
"// MAINTENANCE & CLEANUP": "",
"clean": "node scripts/clean.js",
"clean:all": "node scripts/clean.js --all"
}
}
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.
- 7d ago First seen · 85 lines · 24 tokens per session scan A dacb787046b0
set-up-package-scripts is a skill published in the GitHub repository loerei/chronicle-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 1,157 once invoked, about $0.0001 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-31.
Other skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.