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/long-eval)<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/long-eval"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/long-eval/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/long-eval"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/long-eval.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.00117 | $0.01539 |
| Opus 5.5 | $0.00047 | $0.00616 |
| Sonnet 5.5 | $0.00023 | $0.00308 |
| Haiku 4.5 | $0.00012 | $0.00154 |
Grade A, and why
long-eval 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Long (Restart-Durable) Eval
Role: worker + supervisor. Runs a checkpointed eval that resumes across container recycles, and keeps it alive until it finishes.
Why this exists
A cloud session runs in a container that is recycled on a short cadence (often every few minutes). A recycle kills every running process but keeps the working tree. So any eval longer than one container lifetime must:
- Checkpoint to disk at fine granularity, and resume from the checkpoint rather than restarting — otherwise every recycle throws the work away.
- Be relaunched after each recycle. The session itself is the only supervisor: each recycle re-invokes it ("Continue from where you left off"), which is the relaunch trigger — tighter than any timer.
This skill ships both halves so you don't rebuild them:
| File | Role |
|---|---|
durable_runner.py |
The engine — grades one cell at a time, checkpoints after every sample, resumes at the next unbanked sample. Import it or run via the CLI. |
run_eval.py |
CLI supervisor — run, status, and ensure-alive (the guard-relaunch primitive). |
${CLAUDE_PLUGIN_ROOT} below is the plugin root; from this repo it is
plugins/dev-team.
The eval module contract
An eval module is a plain Python file supplying only the eval-specific bits. Everything durable is handled for you.
SAMPLES = 5 # optional: trials per cell (majority vote)
WORKERS = 10 # optional: moderate on purpose — see note below
def cells(): # -> list of (key, payload)
... # key = a STABLE string, identical every launch
def sample(payload): # -> json-serializable; ONE independent trial
...
def reduce(samples, key, payload): # optional -> the cell's record dict
...
def finalize(done, out_dir): # optional -> summary (once all cells bank)
...
def flag(record): # optional -> bool: force a progress line
...
key is the checkpoint identity — it must be byte-identical across relaunches
(e.g. f"{fixture}||{variant}"). payload is passed straight to sample and
is never persisted, so cells() reconstructs it each launch.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 136 lines · 117 tokens per session scan A de6e2986a6d2
long-eval is a skill published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 117 tokens to every session and 1,539 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-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.