context-usage-mcp: Skill for Codex

.agents/skills/discuss/SKILL.md

discuss is a skill for Codex from beeltec/context-usage-mcp. It costs 38 tokens per session (312 once invoked), scanned A, original, MIT.

A workflow for carrying out an existing task plan from implementation through testing, documentation checks, review, and integration.

In plain words
What is it for?
Executing task breakdowns, creating branches, committing subtasks, running tests, reviewing changes, and merging finished work.
Why use it?
It provides a repeatable path from planned work to completed code. Regular checks and commits make progress easier to verify and recover.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents).

This is beeltec/context-usage-mcp's own configuration. It tells Codex how to work on context-usage-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything context-usage-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to beeltec/context-usage-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/beeltec/context-usage-mcp/main/.agents/skills/discuss/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/beeltec/context-usage-mcp

Made for: Codex.

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 discuss

README.md
[![agentmods](https://agentmods.dev/badge/skills/beeltec/context-usage-mcp/discuss/github.svg)](https://agentmods.dev/skills/beeltec/context-usage-mcp/discuss)
Your own site
<a href="https://agentmods.dev/skills/beeltec/context-usage-mcp/discuss"><img src="https://agentmods.dev/badge/skills/beeltec/context-usage-mcp/discuss/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.

agentmods 80×15 button for discuss

Your own site · 80×15
<a href="https://agentmods.dev/skills/beeltec/context-usage-mcp/discuss"><img src="https://agentmods.dev/badge/skills/beeltec/context-usage-mcp/discuss.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 312 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00038 $0.00312
Opus 5.5 $0.00015 $0.00125
Sonnet 5.5 $0.00008 $0.00062
Haiku 4.5 $0.00004 $0.00031

Measured 2mo ago against content hash 44f708db1e92, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

discuss 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 2mo 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.

.agents/skills/discuss/SKILL.md · 21 lines

What it actually says

Interview me relentlessly about every aspect of this until we reach a shared understanding. Walk down each branch of the decision tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.

Ask the questions one at a time, waiting for feedback on each question before continuing. Asking multiple questions at once is bewildering.

Always use the ask_user_question tool so the user can select an answer from a list of multiple choices. Make sure the first answer is always the one recommended by you and has "(recommended)" as the end of the answer.

If available, always use the context7 mcp to research documentation about tools, frameworks, etc. in question. Also use the web search to find best practices and recommendations on them.

If a fact can be found by exploring the environment (filesystem, tools, etc.), look it up rather than asking me. The decisions, though, are mine — put each one to me and wait for my answer.

Use /wiki to Update the wiki whenever you and the user decide on something or relevant information for the scope of the project come to light.

Do not act on it until I confirm we have reached a shared understanding.

Ask the user if the shared understanding should be documented using /wiki (this is the logical next step). Do so if the user accepts.

Files

What ships with it

1 file 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.

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. 2mo ago First seen · 21 lines · 38 tokens per session scan A 44f708db1e92

Subscribe to this mod's changes

discuss is a skill published in the GitHub repository beeltec/context-usage-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 312 once invoked, about $0.0002 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-31.

Related

Other skills, from other repositories

wikipedia-guide

Gates and identifier chains for the wikipedia tools. Covers switching language editions without reusing titles, disambiguation pages the article tools don't flag, section numbers versus sectionindex, coverage that differs by edition, and the checks to run before calling something absent or sourced. Use when a…

cyanheads/wikipedia-mcp-server · 84 tokens

datalens-editor

Use when authoring or diagnosing DataLens JavaScript Editor table, Gravity, Advanced, Markdown, selector charts, or HTML inside an Editor chart. Not for standalone HTML Pages, native Wizard charts, or independent SDK scripts.

ADIKANT/datalens-dev-mcp · 49 tokens

datalens-dashboard

Use when composing, updating, or visually verifying DataLens dashboard tabs, widgets, selectors, parameters, relations, styles, or layout. Not for standalone HTML Pages, SDK scripts, or metadata-only inspection.

ADIKANT/datalens-dev-mcp · 46 tokens

datalens-dataset-wizard

Use when creating, updating, validating, or previewing DataLens datasets and native Wizard charts. Not for metadata-only reads, cloud identity lookup, standalone HTML, or independent SDK scripting.

ADIKANT/datalens-dev-mcp · 45 tokens

datalens-inspect

Use when reading DataLens metadata, authentication, workbook inventory, relations, current errors, or cloud RLS subject identities without changing objects or access. Not for authoring, backup, or independent SDK scripts.

ADIKANT/datalens-dev-mcp · 47 tokens

datalens-maintenance

Use when exporting DataLens backups, inspecting administrative capabilities, previewing or applying dependency-safe cleanup, or working on standalone HTML Pages. Not for Editor HTML cells, ordinary chart authoring, or RLS identity lookup.

ADIKANT/datalens-dev-mcp · 49 tokens