Borrowing it
Nothing to install: this file belongs to MarcusJellinghaus/mcp-workspace. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MarcusJellinghaus/mcp-workspace/main/.claude/skills/plan_update/SKILL.mdgit clone --depth 1 https://github.com/MarcusJellinghaus/mcp-workspaceWrote 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/marcusjellinghaus/mcp-workspace/plan_update)<a href="https://agentmods.dev/skills/marcusjellinghaus/mcp-workspace/plan_update"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-workspace/plan_update/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/marcusjellinghaus/mcp-workspace/plan_update"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-workspace/plan_update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00007 | $0.00199 |
| Opus 5.5 | $0.00003 | $0.00080 |
| Sonnet 5.5 | $0.00001 | $0.00040 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
plan_update 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- plan_update — 100% identical, 0 lines differ
- plan_update — 97% identical, 0 lines differ
What it actually says
Update Plan Files
Update the implementation plan files in pr_info/steps based on our discussion.
Instructions
Update the plan by modifying the different files in folder pr_info/steps
Please do targeted changes.
Please log the decisions from our discussion in pr_info/steps/Decisions.md.
Only put those decisions that we discussed, no invented decisions.
(For each decision that you log, consider whether you discussed it with me and when I said so)
Guidelines:
- Make minimal, focused changes
- Preserve existing structure where possible
- Ensure consistency across all step files
- Update the summary if scope 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.
- 1mo ago First seen · 28 lines · 7 tokens per session scan A 1e50a2477cb6
plan_update is a skill published in the GitHub repository MarcusJellinghaus/mcp-workspace (48 stars, last pushed today), licensed MIT. It adds 7 tokens to every session and 199 once invoked, about $0.0000 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-08-30.
Other skills, from other repositories
gitnexus-pr-review
Use when the user wants to review a pull request, understand what a PR changes, assess risk of merging, or check for missing test coverage. Examples: "Review this PR", "What does PR #42 change?", "Is this PR safe to merge?".
my-complex-skill
Production-ready Model Context Protocol (MCP) server for multi-agent AI consultations (Codex, Claude, Anti-Gravity, Mimo) with Minimax-M3 consensus synthesis.
gitnexus-debugging
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug".
gitnexus-impact-analysis
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?".
gitnexus-refactoring
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file".
gitnexus-guide
Documents GitNexus itself — available tools, knowledge graph queries, MCP resources, graph schema, and workflow reference. Activated by GitNexus-related questions about tooling, usage, and capabilities.