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 avibebuilder/claude-prime --skill discussgit clone --depth 1 https://github.com/avibebuilder/claude-primeWrote 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/avibebuilder/claude-prime/discuss)<a href="https://agentmods.dev/skills/avibebuilder/claude-prime/discuss"><img src="https://agentmods.dev/badge/skills/avibebuilder/claude-prime/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/avibebuilder/claude-prime/discuss"><img src="https://agentmods.dev/badge/skills/avibebuilder/claude-prime/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.00144 | $0.01118 |
| Opus 5.5 | $0.00058 | $0.00447 |
| Sonnet 5.5 | $0.00029 | $0.00224 |
| Haiku 4.5 | $0.00014 | $0.00112 |
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 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ultrathink
How to think in this mode
The job is to help the user see the decision clearly — what's at stake, what they're missing, where the real tradeoffs are. Engage seriously with their framing: build on it where it holds up, fill in what they haven't named, and push back only when something genuinely doesn't hold up.
Do not implement. Once you start writing code, detailed specs, or execution steps in place of reasoning, you short-circuit the discussion instead of improving it.
Process
Check conversation context and skip completed steps.
1. Clarify (if needed)
- State your understanding of the topic
- Ask focused clarifying questions only when the topic is genuinely ambiguous
2. Ground the discussion (if needed)
- Read relevant files and search the codebase for existing patterns before making claims about the system
- Skip this when the needed facts are already clear from context
3. Pick the right decision lens
Don't force every discussion into the same pros/cons template. Match the lens to the problem:
- Technical or architecture choice — start from constraints, failure modes, maintenance burden, and irreversible decisions
- Product or strategy choice — anchor on user value, business impact, adoption friction, and opportunity cost
- Process or workflow issue — map the current state and bottlenecks before proposing changes
- High-uncertainty or novel territory — surface assumptions, unknowns, and what would invalidate each option
4. Analyze
- Break the problem into its key components
- Surface constraints, dependencies, and hidden assumptions, especially the ones the user has not named explicitly
5. Debate
- Only present options that are genuinely defensible
- If there is truly one strong path, say so directly instead of manufacturing weak alternatives
- Explain the real pros, cons, and tradeoffs of each viable option
- When an assumption looks weak or a constraint is being missed, name it and explain why — but only when there's a real concern, not to seem balanced
- End with a recommendation: "I think X is the right call because..."
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 · 70 lines · 144 tokens per session scan A 23246729c928
discuss is a skill published in the GitHub repository avibebuilder/claude-prime (120 stars, last pushed 5mo ago), licensed MIT. It adds 144 tokens to every session and 1,118 once invoked, about $0.0006 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
chief-data-officer-advisor
Chief Data Officer advisory for startups: AI training data rights and consent provenance, data product strategy (warehouse vs lakehouse vs mesh, build-vs-buy), B2B customer-data-as-asset valuation and M&A readiness, data team org evolution. Use when deciding whether to train models on customer data, choosing data…
contract-and-proposal-writer
Generate professional, jurisdiction-aware business documents: freelance contracts, project proposals, SOWs, NDAs, and MSAs. Structured Markdown output with docx conversion instructions. Covers US (Delaware), EU (GDPR), UK, and DACH (German law) jurisdictions. Not a substitute for legal counsel — use as strong starting…
vpe-advisor
VP of Engineering advisory for startups: delivery throughput (DORA 4 metrics + bottleneck identification), engineering hiring funnel (sourcing → screen → onsite → offer conversion + time-to-fill + pipeline gap), engineering team structure (squad/tribe/chapter design + tech-lead manager-trigger thresholds), and…
process-mapper
Use when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being…
general-counsel-advisor
General Counsel advisory for startups: contract review (MSA, SaaS, NDA, DPA, employment), IP strategy, term sheet decoding, and regulatory landscape mapping. Use when reviewing any contract or term sheet, deciding when to engage outside counsel, defining IP strategy, evaluating regulatory exposure (HIPAA, GDPR, FDA…
strategic-alignment
Cascades strategy from boardroom to individual contributor. Detects and fixes misalignment between company goals and team execution. Covers strategy articulation, cascade mapping, orphan goal detection, silo identification, communication gap analysis, and realignment protocols. Use when teams are pulling in different…