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.
npx skills add leviuszen/meaning-assurance --skill agent-discussiongit clone --depth 1 https://github.com/leviuszen/meaning-assuranceWrote 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/leviuszen/meaning-assurance/agent-discussion)<a href="https://agentmods.dev/skills/leviuszen/meaning-assurance/agent-discussion"><img src="https://agentmods.dev/badge/skills/leviuszen/meaning-assurance/agent-discussion/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/leviuszen/meaning-assurance/agent-discussion"><img src="https://agentmods.dev/badge/skills/leviuszen/meaning-assurance/agent-discussion.svg" alt="Reviewed on agentmods" width="80" 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.00029 | $0.02899 |
| Opus 5.5 | $0.00012 | $0.01160 |
| Sonnet 5.5 | $0.00006 | $0.00580 |
| Haiku 4.5 | $0.00003 | $0.00290 |
Grade A, and why
agent-discussion 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.
How it starts
The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Discussion
Use this skill when Codex needs structured external feedback for planning, architecture review, code discussion, or decision support before making a final call.
Current Path
For read-only external feedback, the current path is:
New-AgentDiscussion.ps1
-> Invoke-ClaudeFeedback.ps1 -Round <1-or-2> -Collect
-> Invoke-ReasonixFeedback.ps1 -Round <1-or-2> -Collect when Reasonix is a reviewer
-> Collect-AgentDiscussion.ps1
-> Codex writes codex-synthesis.md, decision.md, or user-decision-needed.md
If Claude returns a malformed fragment, a file list, or feedback rejected by the format gate, stay in the same discussion folder and use:
Invoke-ClaudeFeedback.ps1 -Round <1-or-2> -RawReadOnlyRecovery -Collect
Do not switch to an unrelated chat or a hand-written direct claude.exe command for this workflow.
Rules
- Codex remains the moderator, evidence evaluator, and final decision maker.
- Discussion mode is read-oriented and file-based.
- Discussion mode does not edit repository files.
- Discussion creation does not launch external agents automatically; use
Invoke-ClaudeFeedback.ps1only when the user wants Claude Code feedback now. - Discussion mode does not create worktrees, merge branches, apply patches, or accept code changes.
- External agents write Markdown feedback files only.
- Reasonix CLI is the automatic review path.
Open-ReasonixDiscussion.ps1remains manual compatibility only and never counts as completion by itself. - Codex writes synthesis, user escalation, and final decision files.
- The default limit is two rounds.
- Pick
-Modefor the task type so the generatedbrief.mdcarries the right output structure. Usearticle-reviewfor article analysis,strategy-reviewfor strategy/planning,code-reviewfor code review,decisionfor option selection, andgeneralotherwise. - Use
-Protocol adversarial-discussionwhen Codex needs debate, synthesis, and a second-round response. Use-Protocol feedbackfor one-way structured feedback. - Use
-ExpectedSectionswhen the user needs named custom sections. This is preferred over prose format instructions. - Use
-ExpectedOutputFormatonly for a complete Markdown template. Prose instructions likeMarkdown with sections: ...are normalized into a strict template and recorded ascustom_normalized. - Use
-ReferencePathswhen the external agent needs to inspect article drafts, source files, notes, or bounded folders. Discussion mode copies read-only snapshots intoreferences/files/and writesreferences/manifest.md; external agents should read those snapshots rather than original absolute paths. - Treat
ReferencePathsas frozen evidence copied at discussion creation time. Round 2 and-RawReadOnlyRecoverystay on the same frozen snapshots. If the original source files changed and the user wants a re-review of current files, create a fresh discussion with new-ReferencePaths. - Reference packaging fails on file-count or size truncation, and both CLI reviewers verify manifest inventory, byte counts, hashes, and evidence bundle identity before review.
- The evidence bundle ID is stored in
status.jsonand derived as SHA-256 over ordered snapshot hashes joined by newlines. - If a major disagreement remains unresolved after two rounds, Codex writes
user-decision-needed.md, pauses, and asks the user to decide or redirect. Agentsare required reviewers.OptionalAgentsare attempted and reported but do not block collection. Do not describe a one-reviewer result as a dual audit.- Use
-AuditProfile scientificfor consequentialcode-reviewandstrategy-reviewwork. Round 1 is blind and independent; Round 2 is limited to disputed, blocking, or weak-evidence findings. - Scientific dual review is complete only when every expected canonical
roundN/<agent>.mdfile exists. Instruction, retry, recovery, and arbitrary Markdown files never count. - Reviewer-local finding IDs must be unique within each canonical file. Duplicate IDs are rejected rather than silently producing ambiguous calibration records.
- Consensus is not proof. Codex adjudicates evidence and records verified outcomes; it does not majority-vote.
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 · 214 lines · 29 tokens per session scan A 0277e4427bdb
agent-discussion is a skill published in the GitHub repository leviuszen/meaning-assurance (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 2,899 once invoked, about $0.0001 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.
Other skills, from other repositories
webgl-particle-galaxy
A real-time particle galaxy — tens of thousands of additive-blended GPU points spiraling around a bright core, their orbits solved entirely in the vertex shader (from glVertexID), so the whole cloud draws in one call. Rendered as a single self-contained index.html. Use when the brief asks for a "particle field"…
webgl-liquid-metal
A real-time liquid-metal shader — a domain-warped noise field shaded as molten chrome, with a sweeping specular highlight over an iridescent thin-film (cosine-palette) sheen. No textures. Rendered as a single self-contained index.html. Use when the brief asks for "liquid metal", "molten chrome", "iridescent"…
webgl-neon-grid
A real-time synthwave scene — a perspective floor grid scrolling toward a banded retro sun under a neon starfield, all from one fragment shader. No textures. Rendered as a single self-contained index.html. Use when the brief asks for "synthwave", "outrun", "retro 80s", "neon grid", "perspective grid", "vaporwave", or…
webgl-holographic-foil
A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.
webgl-horizontal-parallax
A horizontal-scroll WebGL gallery (Three.js): frames glide sideways with lerp smoothing and each image parallaxes its texture (UV shift) by its position in the viewport.
webgl-liquid-iridescence
A self-contained WebGL2 hero: a living oil-on-water field brightened into iridescent caustic filaments; move the cursor to bend the flow.