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/bhanu91221/sfdx-iq/setup-projectgit clone --depth 1 https://github.com/bhanu91221/sfdx-iqWrote 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/bhanu91221/sfdx-iq/setup-project)<a href="https://agentmods.dev/commands/bhanu91221/sfdx-iq/setup-project"><img src="https://agentmods.dev/badge/commands/bhanu91221/sfdx-iq/setup-project.svg" alt="Measured on agentmods" 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 | $0.00029 | $0.00494 |
| Opus 5 | $0.00015 | $0.00247 |
| Sonnet 5 | $0.00006 | $0.00099 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
setup-project 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 4d 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
/setup-project
Copy sfdx-iq rules and configuration templates into the current SFDX project. Use this when npx sfdx-iq setup-project is unavailable (e.g., corporate VPN, blocked npm).
Workflow
Step 1: Verify SFDX Project
Check that sfdx-project.json exists in the current working directory. If missing, inform the user this must be run from an SFDX project root.
Step 2: Locate the Plugin Directory
Use Glob to search for the plugin's CLAUDE.md template in these locations:
~/.claude/plugins/sfdx-iq/.claude-project-template/CLAUDE.md.claude/plugins/sfdx-iq/.claude-project-template/CLAUDE.md**/sfdx-iq/.claude-project-template/CLAUDE.md(fallback broad search)
The plugin root is the parent directory of the found .claude-project-template/ folder.
Step 3: Copy Settings Template
If .claude/settings.json does NOT exist:
- Read
.claude-project-template/settings.jsonfrom the plugin directory - Write it to
.claude/settings.json
If it already exists, skip and inform the user.
Step 5: Copy CLAUDE.md Template
If CLAUDE.md does NOT exist in the project root:
- Read
.claude-project-template/CLAUDE.mdfrom the plugin directory - Write it to
.claude/CLAUDE.mdin the project root
If it already exists, skip and inform the user.
Step 5: Display Summary
Setup Complete
---
Settings: [copied / skipped]
CLAUDE.md: [copied / skipped]
Next steps:
/apex-class --review — Review your Apex code
/code-review — Full code review across Apex, LWC, and Flows
/apex-test — Create or improve Apex test classes
/status — Check plugin and org status
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.
- 4d ago First seen · 52 lines · 29 tokens per session scan A f6bbb1571dc1
setup-project is a command published in the GitHub repository bhanu91221/sfdx-iq (2 stars, last pushed 3mo ago), licensed MIT. It adds 29 tokens to every session and 494 once invoked, about $0.0001 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.