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/PranavNagrecha/AwesomeSalesforceSkillsWrote 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/agents/pranavnagrecha/awesomesalesforceskills/step-tester)<a href="https://agentmods.dev/agents/pranavnagrecha/awesomesalesforceskills/step-tester"><img src="https://agentmods.dev/badge/agents/pranavnagrecha/awesomesalesforceskills/step-tester/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/agents/pranavnagrecha/awesomesalesforceskills/step-tester"><img src="https://agentmods.dev/badge/agents/pranavnagrecha/awesomesalesforceskills/step-tester.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.00041 | $0.00395 |
| Opus 5.5 | $0.00016 | $0.00158 |
| Sonnet 5.5 | $0.00008 | $0.00079 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
step-tester 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 26d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 26d ago First seen · 46 lines · 41 tokens per session scan A 0dd8917caa6f
step-tester is an agent published in the GitHub repository PranavNagrecha/AwesomeSalesforceSkills (24 stars, last pushed 8d ago), with no licence file. It adds 41 tokens to every session and 395 once invoked, about $0.0002 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-10-04.
Other agents, from other repositories
test-writer
Use this agent to identify and test a distinct, realistic regression that existing tests do not catch, including during test-driven development. Do not generate a comprehensive suite by default. Invoke /writing-tests before changing test setup or assertions.\n\nExamples:\n \nContext: The user has just implemented a…
integration-reviewer-r1
R1/R0 tier copy (one effort step lower, never below high) of the integration-reviewer agent. Read-only for repo state (no commits, no source edits that survive) fresh-context reviewer for the merged integration diff across all tasks in an orchestration run — running checks may temporarily mutate the working tree…
rmh
Python specialist sub-agent. Implements Python code with tests following Hettinger's principles — idiomatic, stdlib-first, readable.
tspec-analyst
Test Coverage Analyst agent. Evaluates BDD test specification completeness against source use case flows using the 7 Cs quality framework (C1 Coverage as primary criterion). Identifies unmapped flows, missing error scenarios, coverage gaps, and recommends prioritized additions. Reads both the Feature file and the…
adlc-qa
Tests Agentforce agents and optimizes based on session trace analysis.
typer-expert
Use PROACTIVELY when building, designing, or troubleshooting Python CLI applications with Typer. Specialist for type-hint driven CLI development, command structure, validation, testing, and distribution.