agentmods.dev

update-state

update-state is a skill for Claude Code, Codex from cookjohn/teammcp. It costs 34 tokens per session (498 once invoked), scanned A, original, MIT.

A workflow for changing a project's state field through TeamMCP, a team coordination system for agents. It checks the old value, applies the change, verifies it, and starts an approval request when needed.

In plain words
What is it for?
Use it to change a project field such as status or progress, provide a reason, and confirm the old and new values. It can also request approval and notify the state owner when direct changes are not allowed.
Why use it?
It prevents state changes from being made without checking permissions or confirming the result. It also records why the change was requested and handles cases where someone else owns the field.

Skill for Claude CodeCodex

Part of the fakechat plugin — 9 skills shipped together

not rated 53 2mo ago A scan 34 tokens original MIT
View the source file cookjohn/teammcp
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 skills/cookjohn/teammcp/update-state
Any agent
npx skills add cookjohn/teammcp --skill update-state
Clone the repo
git clone --depth 1 https://github.com/cookjohn/teammcp

Made for: Claude Code, Codex.

Or install fakechat, the plugin that ships this one along with the rest of its 9 skills.

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 update-state

README.md
[![agentmods](https://agentmods.dev/badge/skills/cookjohn/teammcp/update-state.svg)](https://agentmods.dev/skills/cookjohn/teammcp/update-state)
Your own site
<a href="https://agentmods.dev/skills/cookjohn/teammcp/update-state"><img src="https://agentmods.dev/badge/skills/cookjohn/teammcp/update-state.svg" alt="Measured on agentmods" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 498 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.00034 $0.00498
Opus 5 $0.00017 $0.00249
Sonnet 5 $0.00007 $0.00100
Haiku 4.5 $0.00003 $0.00050

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

Security

Grade A, and why

update-state 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.

plugin-dist/templates/skills/update-state/SKILL.md · 46 lines

What it actually says

Update Project State

Instructions

  1. Parse arguments

    • Extract from $ARGUMENTS:
      • project_id — the project identifier
      • field — the state field to update
      • value — the new value to set
      • reason — why this change is being made
    • If any required parameter is missing, ask the user to provide it.

  2. Check current state

    • Call get_state with the project_id to read the current value of the field.
    • Log the current value for reference before making changes.

  3. Attempt to set state

    • Call set_state with project_id, field, value, and reason.
    • If the call succeeds, proceed to verification.

  4. Handle approval flow (if needed)

    • If set_state fails due to ownership or permission restrictions:
      • Call request_approval to submit the state change for approval.
      • Notify the state owner via send_dm that an approval is pending.
      • Report to the user that the change requires approval and is pending.
      • Stop here — do not retry.

  5. Verify the update

    • Call get_state again with the same project_id and confirm the field now holds the new value.
    • Report success with both the old and new values.

  6. Notify if appropriate

    • If the state change is significant (e.g., status transitions like "in-progress" to "done"), send a notification to the relevant channel via send_message.

$ARGUMENTS

  • /update-state <project_id> <field> <value> <reason>
  • Example: /update-state proj-123 status in-review "Feature implementation complete, ready for review"
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 · 46 lines · 34 tokens per session scan A ef0076d2fcc5

Subscribe to this mod's changes

update-state is a skill published in the GitHub repository cookjohn/teammcp (53 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 498 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-30.

Project management
Related

Other skills, from other repositories

timeline-creator

Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.

mhattingpete/claude-skills-marketplace · 47 tokens

bootstrap-prd

Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.

joshukraine/dotfiles · 25 tokens

glab-issue

Create, view, update, and manage GitLab issues. Use when working with issue tracking, bug reports, feature requests, or task management. Operations include creating issues, listing with filters, viewing details, adding comments/notes, updating labels/assignees/milestones, closing/reopening, and board management.…

vince-winkintel/gitlab-cli-skills · 89 tokens

sales-ops

Set up and run Airtable-based sales operations and CRM workflows — pipeline management, account and renewal management, deal desk, RFP / tender pipelines, partner CRMs, sales forecasting, vertical CRMs (real estate, mortgage, brokerage, capital markets, public works, nonprofit), and AI-native lean stacks…

Airtable/skills · 164 tokens

jira

Search and manage Jira issues using JQL queries, create/update tickets, and manage workflows. Use when asked to find Jira tickets, check the backlog, manage sprints, track bugs, or work with Atlassian project management.

odyssey4me/agent-skills · 48 tokens

github

Use this skill when Enoch needs to coordinate work with GitHub: branches, pull requests, issues, reviews, comments, checks, and merges.

our-ark/enoch · 0 tokens