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/nickpolyder/np.copilot.config/resumenpx skills add NickPolyder/NP.CoPilot.Config --skill resumegit clone --depth 1 https://github.com/NickPolyder/NP.CoPilot.ConfigWrote 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/nickpolyder/np.copilot.config/resume)<a href="https://agentmods.dev/skills/nickpolyder/np.copilot.config/resume"><img src="https://agentmods.dev/badge/skills/nickpolyder/np.copilot.config/resume.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 | $0.00040 | $0.01465 |
| Opus 5 | $0.00020 | $0.00732 |
| Sonnet 5 | $0.00008 | $0.00293 |
| Haiku 4.5 | $0.00004 | $0.00146 |
Grade A, and why
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 4d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Intent (anchor): Recover recent repository and session context so work can resume from an accurate next step. Always: gather git, docs, session history, and memory signals; synthesize concise status; identify the most likely next action. Never: fabricate context or expose another user's session data.
Shared policy: Follow
instructions/coordination.instructions.mdfor precedence, invocation, delegation, and handoffs. Followinstructions/session-awareness.instructions.mdfor session continuity.
You are recovering context from previous work sessions so the user can continue seamlessly.
This skill is informational only. It pairs with the session-awareness instruction to recover context, but it does not run an implementation workflow or modify files.
Your goals are to:
- Find recent activity — query session history for work done in this repository.
- Summarize progress — what was accomplished, what's still in progress, what's blocked.
- Reload context — surface relevant plans, task lists, decisions, and open questions.
- Establish next steps — present a clear "here's where you left off, here's what's next."
When to use this skill
Use this skill whenever:
- The user says "continue", "resume", "pick up where I left off", or "what was I working on?"
- The session-awareness instruction finds in-progress work and the user explicitly chooses to continue or recover it.
- The user returns after a break and needs to re-establish context.
Do not use this skill for:
- Searching for specific past sessions by topic — use the session store directly.
- Starting fresh work — just start normally.
- Historical research ("what did I do last month?") — query the session store directly.
Workflow
Step 1: Gather Signals
Check these sources in parallel:
Git State
- Current branch — is it a feature branch? What does the name suggest?
- Uncommitted changes —
git status. Are there work-in-progress modifications? - Recent commits —
git log --oneline -10. What was the last thing committed? - Stashed work —
git stash list. Anything stashed that might be relevant?
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.
- 4d ago First seen · 173 lines · 40 tokens per session scan A 68f63decd345
resume is a skill published in the GitHub repository NickPolyder/NP.CoPilot.Config (2 stars, last pushed 10d ago), licensed MIT. It adds 40 tokens to every session and 1,465 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-31.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…