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 volomydyr/design-engineer-plugin/plugin install design-engineerWrote 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/volomydyr/design-engineer-plugin/meta-statusline)<a href="https://agentmods.dev/skills/volomydyr/design-engineer-plugin/meta-statusline"><img src="https://agentmods.dev/badge/skills/volomydyr/design-engineer-plugin/meta-statusline.svg" alt="Measured on agentmods" 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.00047 | $0.01539 |
| Opus 5 | $0.00023 | $0.00770 |
| Sonnet 5 | $0.00009 | $0.00308 |
| Haiku 4.5 | $0.00005 | $0.00154 |
Grade B, and why
meta-statusline scanned grade B with 1 finding 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 8d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Read `~/.claude/settings.json`. Check whether the `statusLine` field exists. How it starts
The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design-Engineer Status Line
Interaction Method
If AskUserQuestion is available, use it for all prompts below.
If not, present each question as a numbered list and wait for a reply before proceeding.
Step 1: Detect Current Configuration
Read ~/.claude/settings.json. Check whether the statusLine field exists.
If it exists, extract the command value and determine the source:
- Contains
de-statusline.js→ design-engineer status line (already installed) - Contains
gsd-statusline.js→ GSD status line - Anything else → unknown third-party status line
Display what was found.
Step 2: Determine Action
If the command was invoked with an argument:
install→ go to Step 3uninstall→ go to Step 4status→ go to Step 5
Otherwise ask:
question: "What would you like to do with the status line?"
header: "Action"
options:
- label: "Install"
description: "Install the design-engineer status line (replaces any existing one)"
- label: "Uninstall"
description: "Remove the design-engineer status line from settings"
- label: "Check status"
description: "Show current status line configuration"
Step 3: Install
3a. Warn if replacing
If a different status line is currently configured, display:
A status line is already configured:
{current command value}
Installing the design-engineer status line will replace it.
The previous script file will NOT be deleted – only the settings.json pointer changes.
Then ask for confirmation:
question: "Replace the existing status line?"
header: "Confirm"
options:
- label: "Yes, replace it"
description: "Install the design-engineer status line"
- label: "Cancel"
description: "Keep the current status line"
If cancelled, stop.
If the design-engineer status line is already installed, inform the user that it will be updated with the latest version from the plugin.
3b. Copy the script
Create directories if needed:
mkdir -p ~/.claude/hooks ~/.claude/cache
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.
- 8d ago First seen · 212 lines · 47 tokens per session scan B 9d64453b01d9
meta-statusline is a skill published in the GitHub repository volomydyr/design-engineer-plugin (19 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 1,539 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…