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/packagegit 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/package)<a href="https://agentmods.dev/commands/bhanu91221/sfdx-iq/package"><img src="https://agentmods.dev/badge/commands/bhanu91221/sfdx-iq/package.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.00009 | $0.00653 |
| Opus 5 | $0.00005 | $0.00327 |
| Sonnet 5 | $0.00002 | $0.00131 |
| Haiku 4.5 | $0.00001 | $0.00065 |
Grade A, and why
package 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/package
Create and manage second-generation package (2GP) versions for distribution.
Workflow
-
Validate package configuration
- Read
sfdx-project.jsonand locate thepackageDirectorieswithpackageandversionNumberfields - Confirm a package ID exists (starts with
0Ho) - If no package is configured, guide the user through
sf package create - Verify Dev Hub is authenticated
- Read
-
Create package version
- Run:
sf package version create --path <package-directory> --installation-key-bypass --wait 30 --code-coverage - If
--installation-keyis provided, use it instead of--installation-key-bypass - If
--skip-validationflag is set, add it (useful for development iterations) - Monitor creation progress
- Run:
-
Monitor creation
- Package version creation can take 10-30+ minutes
- Poll status with
sf package version create report --package-create-request-id <id> - Report progress updates to the user
- On failure: show error details from the creation request
-
Report results
- Package Version ID: the 04t ID for installation
- Subscriber Package Version ID: for distribution
- Install URL:
https://login.salesforce.com/packaging/installPackage.apexp?p0=<04tId> - Version Number: e.g.,
1.2.0.1 - Ancestry: show package version lineage
- Code Coverage: report overall coverage from validation
- Validation Status: whether the version is validated for release
-
Additional operations
--list: List all package versions withsf package version list --packages <packageId>--promote: Promote a version for production install withsf package version promote --package <04tId>
Flags
| Flag | Description | Default |
|---|---|---|
--installation-key |
Password for package installation | Bypassed |
--skip-validation |
Skip test validation (dev only) | false |
--list |
List existing package versions | false |
--promote |
Promote a version to released | false |
--wait |
Minutes to wait for creation | 30 |
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 · 69 lines · 9 tokens per session scan A 402b526431c1
package is a command published in the GitHub repository bhanu91221/sfdx-iq (2 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 653 once invoked, about $0.0000 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
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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.