Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add bdfinst/agentic-dev-team/plugin install dev-teamWrote 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/bdfinst/agentic-dev-team/continue)<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/continue"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/continue/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/bdfinst/agentic-dev-team/continue"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/continue.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.00063 | $0.00782 |
| Opus 5.5 | $0.00025 | $0.00313 |
| Sonnet 5.5 | $0.00013 | $0.00156 |
| Haiku 4.5 | $0.00006 | $0.00078 |
Grade A, and why
continue 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Continue Session
Role: orchestrator. This command resumes work from a prior session — it does not start new work.
Arguments: optional — a phase or plan name to resume; defaults to the most recent.
You have been invoked with the /continue command.
Orchestrator constraints
- Resume from .claude/memory/ progress files; do not restart completed phases.
- Summarize prior state; do not replay full history.
- Be concise. Report where work resumes, no narration.
Steps
1. Scan for in-progress work
Find phase progress files with Glob(".claude/memory/*.md") — never Read the bare .claude/memory/ directory to see what it contains (${CLAUDE_PLUGIN_ROOT}/knowledge/directory-enumeration.md). These follow the pattern:
.claude/memory/research-progress-*.md— Research phase output.claude/memory/plan-progress-*.md— Plan phase output.claude/memory/implementation-progress-*.md— Implementation phase output.claude/memory/decisions.md— Accumulated decision log
Also check (same rule — Glob, not a directory Read):
plans/directory for active plan filesdocs/specs/for design documents without corresponding implementation — or, on a repo that opted into/specs' issue-first persistence convention, a--spec-issue <url>reference recorded in the active plan instead of a file.claude/review-summaries/for recent review resultscorrections/for unapplied code review fixes
2. Check git state
Run git status and git log --oneline -5 to understand:
- Current branch and its relationship to main
- Any uncommitted changes
- Recent commit messages for context
3. Summarize current state
Present a structured summary:
## Session State
**Branch**: feature/xyz (ahead of main by 3 commits)
**Last phase completed**: Plan (2026-03-17)
**Next phase**: Implement
### In-Progress Work
- [Plan] Widget refactor — 8/12 steps complete
- [Review] 2 unapplied corrections from last review
### Uncommitted Changes
- `src/widget.ts` — modified
- `src/widget.test.ts` — modified
### Recommended Next Action
Continue implementation from step 9 of the widget refactor plan.
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 · 91 lines · 63 tokens per session scan A 028c47da3a39
continue is a skill published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 63 tokens to every session and 782 once invoked, about $0.0003 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-03.
Other skills, from other repositories
mempalace-task
Create, hand off, claim, execute, and close agent tasks through the MemPalace logstream. Use when the user wants to delegate work, prepare a ready-to-paste task for another agent, receive a MemPalace task id, or explicitly launch a supported headless agent in controlled mode.
neat-freak
Knowledge and governance closeout: reconcile project docs, rule files (CLAUDE.md/AGENTS.md), authorized agent memory, and workspace residue with what the code and runtime actually do, so the next session or the next person starts from one current answer. Trigger when the user names "neat-freak", "洁癖", or "/neat" — and…
gsd-mempalace-capture
File a phase artifact into MemPalace; mirror decision facts into its temporal KG.
md-hive-sync
Munder Difflin hive sync — runs the start-of-task hive protocol steps: reads memory.md, checks inbox/ for new messages, and reminds you to record durable facts in memory.md and write coordination files before ending. Use when asked to "sync with the hive", "check my inbox", "hive status", or "hive sync". Proactively…
commonly
You are a member of a Commonly workspace — a shared space where humans and AI agents from any origin collaborate in pods (chat rooms with memory). Use this whenever you are connected to Commonly via the commonly MCP tools: to read what's happening, post, remember things across sessions, react, DM other agents, and…
rem-page-org
What an organisation's page in the notebook is made of — the fixed sections, when a company earns a page at all instead of staying a field on a person's, and the rules that keep it from becoming a second copy of everyone who works there. Composed into every stage that writes one.