implementation-session

implementation-session is a skill for Claude Code, Codex from mattmre/EVOKORE-MCP-PUBLIC. It costs 28 tokens per session (417 once invoked), scanned A, original, MIT.

A workflow for starting a coding session by reviewing priorities, checking branches, coordinating implementation work, and closing the session properly.

In plain words
What is it for?
It is for reviewing project notes, finding the highest-priority tasks, checking stale branches, planning implementation, and coordinating coding work.
Why use it?
It gives a large or ongoing project a repeatable way to choose the next work and avoid losing changes or context.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions CLAUDE.md.

Good fit It is for reviewing project notes, finding the highest-priority tasks, checking stale branches, planning implementation, and coordinating coding work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mattmre/evokore-mcp-public/implementation-session
Install

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.

Any agent
npx skills add mattmre/EVOKORE-MCP-PUBLIC --skill implementation-session
Clone the repo
git clone --depth 1 https://github.com/mattmre/EVOKORE-MCP-PUBLIC

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for implementation-session

README.md
[![agentmods](https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/implementation-session/github.svg)](https://agentmods.dev/skills/mattmre/evokore-mcp-public/implementation-session)
Your own site
<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/implementation-session"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/implementation-session/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.

agentmods 80×15 button for implementation-session

Your own site · 80×15
<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/implementation-session"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/implementation-session.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 417 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.00417
Opus 5.5 $0.00011 $0.00167
Sonnet 5.5 $0.00006 $0.00083
Haiku 4.5 $0.00003 $0.00042

Measured 1mo ago against content hash 36db5329a5a5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

implementation-session 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.

SKILLS/GENERAL CODING WORKFLOWS/implementation-session/SKILL.md · 36 lines

What it actually says

Implementation Session

This skill executes a complete implementation cycle from planning through orchestration and final session wrap-up.

Core Workflows

1. Priority Identification

  • Review CLAUDE.md and next-session.md (or equivalent).
  • Show the next top 5, or up to top 15 priority items or phases.
  • Before implementing anything, review the exact solution we will implement given the parameters to ensure understanding.

2. Stale Local Branches

  • Walk through "stale local branches" both locally and in the online repo.
  • Ensure they are accounted for in GitHub so we aren't losing anything vital. No short or quick scans.
  • Check if local repos have changes that were not merged or committed, or might be from partial sessions that were not completed/logged properly. Fix as needed.

3. Agentic Implementation

  • Use agentic orchestration to complete implementation of these items.
  • I want no context rot, so please orchestrate and provide agents with instructions and plans as needed to accomplish tasks, then dispose of the agent and use another fresh agent as you move through the work.
  • Please research and plan/architect all features before implementation.
  • Coordinate analysis of current research and docs within the repo as needed (we have extensive research but may need more).
  • If research is done, please make sure to document and save that to the docs folder for tracking and future use.
  • Keep track of the session log and agents' work so we can track and monitor.
  • Orchestrate and then make a PR for each so we can review.

4. Session Wrap

  • Close the session and update the session log.
  • Update next-session.md and prepare for the next session.
  • (Keep in mind there may be another session running that just completed; incorporate its handoff points if applicable.)
Changes

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.

  1. 1mo ago First seen · 36 lines · 28 tokens per session scan A 36db5329a5a5

Subscribe to this mod's changes

implementation-session is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 5mo ago), licensed MIT. It adds 28 tokens to every session and 417 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

acceptance-orchestrator

Use when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.

LiHongwei-cn/lihongwei-cn · 37 tokens

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

create-milestone

Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.

agentic-community/mcp-gateway-registry · 64 tokens

connect

Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…

nimbalyst/nimbalyst · 101 tokens

internal-comms

Author clear, high-impact internal engineering communications including 3P status updates, blameless incident postmortems, architecture decision memos, and leadership briefs. Use when writing technical updates, sprint reports, incident reviews, or organizational engineering announcements.

WrongStack/WrongStack · 53 tokens

nw-finalize

Archives a completed feature to docs/evolution/, migrates lasting artifacts to permanent directories, and cleans up the temporary workspace. Use after all implementation steps pass and mutation testing completes.

nWave-ai/nWave · 39 tokens