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 HirogaKatageri/hirokata --skill discussgit clone --depth 1 https://github.com/HirogaKatageri/hirokataWrote 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/hirogakatageri/hirokata/discuss)<a href="https://agentmods.dev/skills/hirogakatageri/hirokata/discuss"><img src="https://agentmods.dev/badge/skills/hirogakatageri/hirokata/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.
<a href="https://agentmods.dev/skills/hirogakatageri/hirokata/discuss"><img src="https://agentmods.dev/badge/skills/hirogakatageri/hirokata/discuss.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.00095 | $0.01199 |
| Opus 5 | $0.00048 | $0.00600 |
| Sonnet 5 | $0.00019 | $0.00240 |
| Haiku 4.5 | $0.00010 | $0.00120 |
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 today.
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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discuss — Context Summarizer and Discussion Facilitator
Analyze the current conversation context, surface the subjects it contains, and facilitate a focused discussion with the user — either across all topics or scoped to one specific topic.
Two Modes
Mode 1: Open Discussion (/discuss or discuss)
No topic argument given. Scan the full conversation context.
Step 1 — Extract subjects
Read the conversation and identify all distinct subjects, decisions, problems, questions, and themes present. Group closely related items under a single subject heading. Aim for 3–8 groups; merge very small or overlapping ones.
Step 2 — Present the topic map
Display a numbered list of subjects with a one-sentence summary for each:
Context Summary
===============
Subjects found in this conversation:
1. <Subject Title>
<One-sentence description of what was discussed or decided.>
2. <Subject Title>
<One-sentence description.>
3. <Subject Title>
<One-sentence description.>
Which subject would you like to discuss? (enter a number, name, or "all")
Step 3 — Enter discussion loop
Wait for the user to pick a subject or say "all". Then enter the discussion loop (see below).
Mode 2: Targeted Discussion (discuss [topic])
A topic argument was given. Scope analysis to that topic only.
Step 1 — Find relevant context
Search the conversation for everything related to the given topic: decisions made, problems raised, open questions, referenced files or code, dependencies, and constraints.
Step 2 — Present the topic summary
Discussion: <Topic>
===================
Summary
-------
<2–4 sentence narrative summary of everything the context says about this topic.>
Key points:
• <point>
• <point>
• <point>
Open questions or unresolved items:
• <item> (or "None" if everything is settled)
What would you like to explore or decide about [topic]?
Then enter the discussion loop immediately.
Discussion Loop
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.
- today Changed 35ea1fab1878
- 9d ago First seen · 170 lines · 95 tokens per session scan A 7d5c1ad0a7c4
discuss is a skill published in the GitHub repository HirogaKatageri/hirokata (5 stars, last pushed yesterday), licensed MIT. It adds 95 tokens to every session and 1,199 once invoked, about $0.0005 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-31.
Other skills, from other repositories
unslop
Humanize LLM output so it reads like a careful human wrote it. Subtracts AI-isms (sycophancy, tricolons, em-dash overuse, "delve"/"tapestry"/"testament", hedging stacks, tidy five-paragraph shapes), engineers burstiness and calibrated uncertainty, and preserves technical accuracy. Supports intensity levels: subtle…
unslop-file
Humanize natural-language memory files (CLAUDE.md, todos, preferences, docs) by removing AI-isms and adding burstiness while preserving every code block, URL, path, command, and heading exactly. Two modes: --deterministic (fast, regex-based, no API) and LLM (default, calls Claude for rewrite). Humanized version…
unslop-commit
Rewrites commit messages so they sound like a careful human engineer wrote them. Strips AI/marketing slop ("comprehensive solution", "robust implementation", "leverage", "enhance", "seamlessly", "This commit..."). Keeps Conventional Commits format. Subject ≤72 chars (aim ≤50), imperative mood. Body only when "why"…
unslop-help
Quick-reference card for unslop modes, sub-skills, and slash commands. One-shot display, not a persistent mode. Trigger: /unslop-help, "unslop help", "what unslop commands", "how do I use unslop".
simulator-charts
Simulator.Company chart and dashboard specialist. Use when the user wants to create, configure, or query charts (line, bar, area), dashboards, or financial time-series visualisations on a graph layer. Trigger on any of these intents: — Creating: "create chart", "add chart", "create dashboard", "add dashboard", "build…
simulator-init
Simulator.Company environment setup specialist. Use when the user wants to connect to Simulator.Company, set up credentials, authenticate, configure the workspace, or start working with Simulator for the first time. Activate when the user says "init", "setup", "connect to simulator", "login to simulator", "configure…