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 cogni-work/insight-wave --skill website-resumegit clone --depth 1 https://github.com/cogni-work/insight-waveWrote 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/cogni-work/insight-wave/website-resume)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/website-resume"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/website-resume/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/cogni-work/insight-wave/website-resume"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/website-resume.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.00117 | $0.01148 |
| Opus 5.5 | $0.00047 | $0.00459 |
| Sonnet 5.5 | $0.00023 | $0.00230 |
| Haiku 4.5 | $0.00012 | $0.00115 |
Grade A, and why
website-resume 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 1mo 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Website Resume
Detect the current state of a website project, show progress, and route to the appropriate next skill.
Workflow
1. Find Website Project
Scan for website-project.json in:
- Current directory
- Immediate child directories matching
cogni-website*or*-website
If not found, inform the user and suggest website-setup.
2. Assess Project State
Read available files and determine the project phase:
| File Exists | Phase | Status |
|---|---|---|
website-project.json only |
Setup complete | Needs plan |
+ website-plan.json |
Plan complete | Needs build |
+ output/website/index.html |
Build complete | Ready for preview |
+ output/website/css/style.css + pages |
Fully built | Ready for deployment |
Count:
- Pages planned (from website-plan.json)
- Pages built (HTML files in output/website/)
- Missing pages (planned but not built)
- Content source freshness (compare source file dates to build dates)
3. Present Status
Website-Projekt: {slug}
Phase: {current phase}
Unternehmen: {company name}
Theme: {theme name}
Sprache: {language}
Geplante Seiten: {N}
Erstellte Seiten: {M} / {N}
Fehlende Seiten: {list if any}
Rechtliches:
Rechtsordnung: {jurisdiction or "noch nicht festgelegt"}
Legal Pages: {3/3 generiert | 0/3 fehlen | ⚠ legal_config fehlt}
Offene TODOs: {n unfilled «TODO: ...» markers}
Letzte Änderung: {date}
When assessing legal state, read legal_config.jurisdiction from website-project.json, scan website-plan.json for legal-* page entries, and grep content/legal/*.md for any «TODO: markers.
4. Recommend Next Action
Based on the state:
| State | Recommendation |
|---|---|
| Setup complete, no plan | → /website-plan — Seitenstruktur planen |
| Plan complete, no build | → /website-build — Website generieren |
| Build complete | → /website-preview — Website prüfen |
| Build outdated (sources newer than build) | → /website-build — Website aktualisieren (Quellen geändert) |
| Partially built (some pages missing) | → /website-build — Fehlende Seiten generieren |
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.
- 1mo ago First seen · 119 lines · 117 tokens per session scan A 3bce357c0d4d
website-resume is a skill published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 117 tokens to every session and 1,148 once invoked, about $0.0005 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-09-04.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.