agentmods.dev

dev-thread-manager

dev-thread-manager is an agent for coding agents from Emasoft/ghe-marketplace. It costs 137 tokens per session (5,800 once invoked), scanned A, original, MIT.

An agent for managing development-work threads, including starting work, resuming it, recording checkpoints, and moving it to testing.

In plain words
What is it for?
Creating and claiming development threads, posting progress checkpoints, and transitioning completed development work to testing.
Why use it?
It keeps code-heavy work organized across defined stages and records where the work stands. It also applies the user's specifications as written.

Agent

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the ghe plugin — 10 skills, 2 commands, 10 agents, 5 hooks shipped together

not rated 4 9mo ago A scan 137 tokens original MIT
View the source file Emasoft/ghe-marketplace
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.

agentmods
npx agentmods add agents/emasoft/ghe-marketplace/dev-thread-manager
Clone the repo
git clone --depth 1 https://github.com/Emasoft/ghe-marketplace

Or install ghe, the plugin that ships this one along with the rest of its 10 skills, 2 commands, 10 agents, 5 hooks.

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 dev-thread-manager

README.md
[![agentmods](https://agentmods.dev/badge/agents/emasoft/ghe-marketplace/dev-thread-manager.svg)](https://agentmods.dev/agents/emasoft/ghe-marketplace/dev-thread-manager)
Your own site
<a href="https://agentmods.dev/agents/emasoft/ghe-marketplace/dev-thread-manager"><img src="https://agentmods.dev/badge/agents/emasoft/ghe-marketplace/dev-thread-manager.svg" alt="Measured on agentmods" height="20"></a>
Per session 137 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,800 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00137 $0.05800
Opus 5 $0.00068 $0.02900
Sonnet 5 $0.00027 $0.01160
Haiku 4.5 $0.00014 $0.00580

Measured 4d ago against content hash 76f0b2a815aa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dev-thread-manager 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.

plugins/ghe/agents/dev-thread-manager.md · 718 lines

How it starts

The opening of the file, as written. The whole thing — 718 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Quick References

Shared Documentation (see agents/references/):

IRON LAW: User Specifications Are Sacred

THIS LAW IS ABSOLUTE AND ADMITS NO EXCEPTIONS.

  1. Every word the user says is a specification - follow verbatim, no errors, no exceptions
  2. Never modify user specs without explicit discussion - if you identify a potential issue, STOP and discuss with the user FIRST
  3. Never take initiative to change specifications - your role is to implement, not to reinterpret
  4. If you see an error in the spec, you MUST:
    • Stop immediately
    • Explain the potential issue clearly
    • Wait for user guidance before proceeding
  5. No silent "improvements" - what seems like an improvement to you may break the user's intent

Violation of this law invalidates all work produced.

Background Agent Boundaries

When running as a background agent, you may ONLY write to:

  • The project directory and its subdirectories
  • The parent directory (for sub-git projects)
  • ~/.claude (for plugin/settings fixes)
  • /tmp

Do NOT write outside these locations.

Settings Awareness

Check .claude/ghe.local.md for project settings:

  • enabled: If false, skip all GitHub Elements operations
  • warnings_before_enforce: Number of warnings before blocking
  • auto_worktree: ALWAYS true - worktrees are mandatory
  • serena_sync: If true, sync checkpoints to SERENA memory bank

Defaults if no settings file: enabled=true, warnings_before_enforce=3, auto_worktree=true, serena_sync=true

GHE_REPORTS Rule (MANDATORY)

ALL reports MUST be posted to BOTH locations:

  1. GitHub Issue Thread - Full report text (NOT just a link!)
  2. GHE_REPORTS/ - Same full report text (FLAT structure, no subfolders!)

Read the full file on GitHub · 718 lines

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. 4d ago First seen · 718 lines · 0 tokens per session scan A 76f0b2a815aa

Subscribe to this mod's changes

dev-thread-manager is an agent published in the GitHub repository Emasoft/ghe-marketplace (4 stars, last pushed 9mo ago), licensed MIT. It adds 137 tokens to every session and 5,800 once invoked, about $0.0007 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.

Project management
Related

Other agents, from other repositories

scrum-master

Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.

LuisFelipeMoro/Harness-devkit · 24 tokens

Orchestrator

Task coordination and agent delegation.

SylphxAI/coderag · 9 tokens

project-manager

Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.

mysleekdesigns/crawlforge-mcp · 46 tokens

nexus

Turn one user task into a coherent, verified integration-branch delivery by coordinating the smallest safe adaptive workflow.

Stivi7/cyberpunk-context-runners · 0 tokens

pm-advisor

You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".

VandanaAjayDubey111/great-pm · 123 tokens

tidier

PM subagent that maintains board hygiene every PM continuation turn and returns maintenance schema 0.2.2. Idempotent -- detects nothing-to-do and returns quickly. Responsibilities: BOARD.md index rebuild (when out-of-sync), stale claim reclamation, archived scratch file cleanup, systemic pattern logging, and scratch…

GhostlyGawd/engineering-board · 77 tokens