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.
git clone --depth 1 https://github.com/rdmgator12/RE-MCP-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.
[](https://agentmods.dev/commands/rdmgator12/re-mcp-/ncci-check)<a href="https://agentmods.dev/commands/rdmgator12/re-mcp-/ncci-check"><img src="https://agentmods.dev/badge/commands/rdmgator12/re-mcp-/ncci-check/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/commands/rdmgator12/re-mcp-/ncci-check"><img src="https://agentmods.dev/badge/commands/rdmgator12/re-mcp-/ncci-check.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.00000 | $0.00271 |
| Opus 5 | $0.00000 | $0.00135 |
| Sonnet 5 | $0.00000 | $0.00054 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
ncci-check 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 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.
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.
What it actually says
/ncci-check
Check NCCI PTP edits between two or more CPT/HCPCS codes.
Usage
/ncci-check <code1> <code2> [--hospital] [--disclosure]
/ncci-check <code1> <code2> <code3> ... [--hospital]
Examples
/ncci-check 29881 29877
/ncci-check 27447 20610 77002 --hospital
/ncci-check 63030 63035 77003 20930 --disclosure
What It Does
Two codes:
- Checks both directional NCCI PTP edits
- Returns modifier indicator (can unbundle or cannot)
- Recommends specific modifier if applicable
- Shows edit rationale and effective date
Three or more codes:
- Runs full
bundle_analyzeron all codes - Checks all pairwise NCCI edits
- Determines which codes are payable vs bundled
- Calculates expected total Medicare payment
- Provides recommended billing with modifiers
Tools Used
check_ncci_edits— For two-code checksbundle_analyzer— For three or more codesmodifier_advisor— For modifier recommendations
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 · 40 lines · 0 tokens per session scan A 3258fb1b367b
ncci-check is a command published in the GitHub repository rdmgator12/RE-MCP- (0 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 271 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.