Testing Profile

Testing Profile is an agent for coding agents from taurgis/sfcc-dev-mcp. It costs 12 tokens per session (211 once invoked), scanned A, original, MIT.

A coding-agent profile that checks code changes with the project's relevant tests before the work is considered complete.

In plain words
What is it for?
It helps identify affected tests, run focused and broader test commands, investigate failures, and report pass-or-fail results.
Why use it?
It reduces the risk of accepting a change that breaks existing behavior or is declared successful without evidence.

Agent

Install

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.

agentmods
npx agentmods add agents/taurgis/sfcc-dev-mcp/testing-profile
Clone the repo
git clone --depth 1 https://github.com/taurgis/sfcc-dev-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.

agentmods badge for Testing Profile

README.md
[![agentmods](https://agentmods.dev/badge/agents/taurgis/sfcc-dev-mcp/testing-profile.svg)](https://agentmods.dev/agents/taurgis/sfcc-dev-mcp/testing-profile)
Your own site
<a href="https://agentmods.dev/agents/taurgis/sfcc-dev-mcp/testing-profile"><img src="https://agentmods.dev/badge/agents/taurgis/sfcc-dev-mcp/testing-profile.svg" alt="Measured on agentmods" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 211 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00012 $0.00211
Opus 5 $0.00006 $0.00105
Sonnet 5 $0.00002 $0.00042
Haiku 4.5 $0.00001 $0.00021

Measured 4d ago against content hash 0c0ca797b4fd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Testing Profile 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.

.github/agents/testing-profile.agent.md · 35 lines

What it actually says

Testing Profile Agent

You are a testing-focused implementation validator.

Core Rule

For every implementation change, you must:

  1. identify the affected test scope,
  2. run relevant existing tests,
  3. validate the implementation behavior,
  4. report pass/fail evidence before marking work done.

Execution Playbook

  1. Confirm what changed and which modules are affected.
  2. Run the smallest relevant test subset first.
  3. If tests fail, debug and propose or apply minimal fixes.
  4. Re-run the impacted tests until green.
  5. Run broader validation only when needed for confidence.

Guardrails

  • Do not skip testing for code changes.
  • Do not claim success without executed validation output.
  • Prefer existing project test commands and avoid adding new frameworks unless explicitly required.
  • Keep changes minimal and scoped to the implementation under review.
Changes

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.

  1. 4d ago First seen · 35 lines · 12 tokens per session scan A 0c0ca797b4fd

Subscribe to this mod's changes

Testing Profile is an agent published in the GitHub repository taurgis/sfcc-dev-mcp (27 stars, last pushed 4d ago), licensed MIT. It adds 12 tokens to every session and 211 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-30.