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 ChenShuo2004/cs-skills --skill cs-ending-timegit clone --depth 1 https://github.com/ChenShuo2004/cs-skillsWrote 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/chenshuo2004/cs-skills/cs-ending-time)<a href="https://agentmods.dev/skills/chenshuo2004/cs-skills/cs-ending-time"><img src="https://agentmods.dev/badge/skills/chenshuo2004/cs-skills/cs-ending-time/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/chenshuo2004/cs-skills/cs-ending-time"><img src="https://agentmods.dev/badge/skills/chenshuo2004/cs-skills/cs-ending-time.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 38 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00031 | $0.02247 |
| Opus 5 | $0.00015 | $0.01123 |
| Sonnet 5 | $0.00006 | $0.00449 |
| Haiku 4.5 | $0.00003 | $0.00225 |
Grade A, and why
cs-ending-time 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 9d 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ending Time
Purpose
Use this skill as the final-mile delivery workflow for web and app projects.
Task Isolation (required)
This workflow closes only one bounded delivery at a time. Before any staging, commit, push, or deploy action:
- Bind one delivery target explicitly: feature/ticket name, route(s), data, and expected output.
- Run in a single repository target (do not mix parent and nested repos).
- Confirm branch and target files are scoped to that single delivery.
- Ignore unrelated worktree changes and never stage them in this workflow.
- Do not reuse deployment URLs, commit SHAs, or validation artifacts from another delivery.
If multiple tasks are detected in the same conversation or worktree, ask to split and finish one task before moving to the next.
The goal is to turn a requested page or feature into a verified delivery: requirements understood, implementation scoped, checks run, Git history clean, GitHub updated, Vercel deployment verified, and the user left with exact links and remaining risks.
Production Deployment Concurrency (required)
A production URL, Vercel production alias, or production branch is a shared mutable target. Preview deployments can run in parallel, but anything that can change production must be serialized.
Before running any command that can change production, including vercel --prod, vercel promote, vercel alias set, or pushing to a branch that auto-deploys production:
- Derive a lock key from the repository remote, Vercel project name, and production domain or alias.
- Acquire an exclusive local lock before the production-mutating command. Prefer an atomic directory lock under
$env:TEMP\cs-ending-time-locks\<lock-key>.lock; record repo root, branch, base commit, target commit, deployment URL, Vercel project, alias/domain, timestamp, and delivery target in the lock metadata. - If the lock already exists, do not deploy over it. Inspect the metadata, report the active delivery, and wait or ask the user which delivery owns production.
- Build and verify a unique preview deployment first. Only promote that exact deployment after holding the lock.
- After acquiring the lock, re-check the current production state with
git fetch, the target branch HEAD, andvercel inspector the Vercel dashboard. If production advanced after the preview was built, stop and rebuild/rebase instead of promoting stale output. - Release the lock only after production verification and closeout. Treat stale locks as unsafe unless the user confirms they are abandoned.
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.
- 9d ago First seen · 202 lines · 31 tokens per session scan A 2e781cf2e419
cs-ending-time is a skill published in the GitHub repository ChenShuo2004/cs-skills (141 stars, last pushed 6d ago), licensed MIT. It adds 31 tokens to every session and 2,247 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
land-and-deploy
Land and deploy workflow. (gstack).
publish-site
Versioned site deploys to GitHub/Cloudflare/Netlify Pages.
land-and-deploy
Land and deploy workflow. Merges the PR, waits for CI and deploy, verifies production health via canary checks. Takes over after /ship creates the PR. Use when: "merge", "land", "deploy", "merge and verify", "land it", "ship it to production". (gstack).
deploy
Deploy latest master to production with a version tag. Use when releasing to production or tagging a deploy.
ship
Use when code is ready to ship — creates PRs, merges, deploys, and verifies. Handles the full PR-to-production pipeline. Triggers on /ship.
aws-serverless-rollout-corrector
Patch AWS serverless rollout definitions across Lambda, API Gateway, EventBridge, SQS, SNS, event source wiring, aliases, versions, and deployment config. Prefer this for repo-side rollout corrections; do not perform live rollout actions or destructive operations.