Borrowing it
Nothing to install: this file belongs to wghglory/ngx-lift-workspace. 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/wghglory/ngx-lift-workspace/main/.cursor/skills/create-month-swag/SKILL.mdgit clone --depth 1 https://github.com/wghglory/ngx-lift-workspaceWrote 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/wghglory/ngx-lift-workspace/create-month-swag)<a href="https://agentmods.dev/skills/wghglory/ngx-lift-workspace/create-month-swag"><img src="https://agentmods.dev/badge/skills/wghglory/ngx-lift-workspace/create-month-swag/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/wghglory/ngx-lift-workspace/create-month-swag"><img src="https://agentmods.dev/badge/skills/wghglory/ngx-lift-workspace/create-month-swag.svg" alt="Reviewed on agentmods" width="80" 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.00044 | $0.00556 |
| Opus 5.5 | $0.00018 | $0.00222 |
| Sonnet 5.5 | $0.00009 | $0.00111 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
create-month-swag 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 16d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Execution Plan & Monthly SWAG
Breaks down project requirements, design specifications, and technical estimates into a structured, achievable month-by-month execution plan.
Instructions
- Analyze Dependencies: Identify the critical path. Determine prerequisite utilities, data models, or infrastructure before dependent features can start.
- Chunk by Value (Initiatives): Group work into initiatives that deliver verifiable, testable milestones within ~4-week cycles.
- Validate Timing: Use complexity analysis to ensure each month is achievable, with contingency for edge cases and testing.
- Structured Markdown Output: Produce the plan adhering to the standard hierarchy below.
Output Format
# Project Execution Plan: [Project Name]
## 1. Executive Summary
| Month | Initiative Theme | Primary Goal | Key Dependencies |
| :---------- | :--------------- | :----------- | :--------------- |
| **Month 1** | ... | ... | ... |
| **Month 2** | ... | ... | ... |
## 2. Visual Timeline
```mermaid
gantt
dateFormat YYYY-MM-DD
title Project Execution Timeline
section Month 1
Core Foundation :done, m1_1, 2026-10-01, 14d
Initial Components :active, m1_2, after m1_1, 14d
section Month 2
Feature Integration :m2_1, after m1_2, 21d
Testing & Hardening :m2_2, after m2_1, 7d
```
## 3. Detailed Monthly Breakdown
### Month 1: [Initiative Name]
**Focus:** One sentence summary of the core value delivered.
- **Key Deliverables:**
- [ ] **[Component/Area]**: [Task Description] (Est: X Days)
- [ ] **[Component/Area]**: [Task Description] (Est: Y Days)
- **Dependencies Resolved:** What blockers are cleared for subsequent months?
- **Risks & Unknowns:** Flag technical risks or integration questions.
- **Definition of Done:** Verifiable acceptance criteria for this month (tests passing, builds clean).
---
## 4. Parking Lot / Out of Scope
Items from the requirements that are deferred to later phases.
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.
- 16d ago First seen · 68 lines · 44 tokens per session scan A f2d508666d75
create-month-swag is a skill published in the GitHub repository wghglory/ngx-lift-workspace (7 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 556 once invoked, about $0.0002 per session on Opus 5.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-10-02.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…