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 agentmods add commands/intellegix/intellegix-code-agent-toolkit/stub-checkgit clone --depth 1 https://github.com/intellegix/intellegix-code-agent-toolkitWhat 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 | $0.00000 | $0.06906 |
| Opus 5 | $0.00000 | $0.03453 |
| Sonnet 5 | $0.00000 | $0.01381 |
| Haiku 4.5 | $0.00000 | $0.00691 |
Grade A, and why
stub-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 3d 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 — 642 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/stub-check — Deep Implementation Completeness Audit
Perform a thorough 3-phase audit of the current project's codebase to find code that is unfinished, shallow, skeletal, or not production-ready. Phase 0.5 runs a Perplexity research reconnaissance using GitHub connectors (runs in parallel with Phase 1). Phase 1 uses local scanning (Grep/Glob/Read) independently. Phase 2 merges both passes through Perplexity for final depth/brevity validation.
Architecture: Research recon (Perplexity + GitHub connectors) runs IN PARALLEL with local pattern scan → merge → research validation last (depth + brevity). ~90s total overhead. $0 cost via Perplexity login session.
CRITICAL: Do NOT ask the user questions before completing all phases. Execute the full audit silently and present results at the end. Only interact if $ARGUMENTS specifies a subset of the codebase to audit.
Input
$ARGUMENTS = Optional path or module to audit (e.g., automated-loop/, src/auth/). If empty, audit the entire project from the working directory.
Step 0: Detect Project Languages — MANDATORY, SILENT
Before scanning, auto-detect which languages and frameworks are present. This determines which pattern sets to use.
-
Check for language markers (run in parallel):
Globfor**/*.py→ Python detectedGlobfor**/*.tsor**/*.tsx→ TypeScript detectedGlobfor**/*.jsor**/*.jsx→ JavaScript detectedGlobfor**/*.go→ Go detectedGlobfor**/*.rs→ Rust detectedGlobfor**/*.javaor**/*.kt→ Java/Kotlin detectedGlobfor**/*.rb→ Ruby detectedGlobfor**/*.cs→ C# detectedGlobfor**/*.swift→ Swift detectedGlobfor**/*.cor**/*.cppor**/*.h→ C/C++ detectedGlobfor**/*.php→ PHP detected
-
Check for framework markers (read if they exist):
package.json→ checkdependenciesfor React, Next.js, Express, Fastify, NestJS, Vue, Angular, Sveltepyproject.tomlorsetup.py→ check for Django, Flask, FastAPI, SQLAlchemyCargo.toml→ Rust crate metadatago.mod→ Go module metadataGemfile→ Ruby gemspom.xmlorbuild.gradle→ Java/Kotlin build system*.csprojor*.sln→ .NET project
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.
- 3d ago First seen · 642 lines · 0 tokens per session scan A 269ad9682a99
stub-check is a command published in the GitHub repository intellegix/intellegix-code-agent-toolkit (57 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 6,906 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-30.
Other commands, from other repositories
README
Git workflow and quality assurance commands for the claude-skills repository.
loop
Iteratively fix issues until all resolved or max iterations reached.
OpenSpec: Apply
Implement an approved OpenSpec change and keep tasks in sync.
auto-goal
goal 래퍼 — /goal 생성, 상태 확인, 완료/blocked handoff를 goal tool 또는 slash command로 연결합니다.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
implement-task
根据技术方案实施任务并输出实现报告.