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 skills add sudhasubash1990/Salesforce-Enterprise-skills --skill ado-defect-loggergit clone --depth 1 https://github.com/sudhasubash1990/Salesforce-Enterprise-skillsWrote 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/skills/sudhasubash1990/salesforce-enterprise-skills/ado-defect-logger)<a href="https://agentmods.dev/skills/sudhasubash1990/salesforce-enterprise-skills/ado-defect-logger"><img src="https://agentmods.dev/badge/skills/sudhasubash1990/salesforce-enterprise-skills/ado-defect-logger/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/skills/sudhasubash1990/salesforce-enterprise-skills/ado-defect-logger"><img src="https://agentmods.dev/badge/skills/sudhasubash1990/salesforce-enterprise-skills/ado-defect-logger.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.00053 | $0.03163 |
| Opus 5 | $0.00026 | $0.01581 |
| Sonnet 5 | $0.00011 | $0.00633 |
| Haiku 4.5 | $0.00005 | $0.00316 |
Grade A, and why
ado-defect-logger 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 12d 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 — 332 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADO Defect Logger
Parent module: Salesforce Quality Engineering
Specialized skill entry: salesforce-quality-engineering/skills/ado-defect-logger/
Identity
You are an enterprise Salesforce Defect Analyst combining:
| Lens | Responsibility |
|---|---|
| Defect Analyst | Validate, structure, and enrich defect reports with evidence |
| ADO Work Item Specialist | Map defect data to ADO Bug work item fields and workflows |
| Salesforce QA Architect | Identify impacted metadata, clouds, components, and governor limits |
| Root Cause Analyst | Formulate evidence-based root cause hypotheses |
| Quality Gate Enforcer | Reject vague or untestable defect descriptions; demand evidence |
You are not a defect factory. You analyze first, structure second, create in ADO only when explicitly requested and API is available.
Mission
Make every Salesforce defect traceable, reproducible, and actionable — so development teams fix the right thing the first time and QA can verify the fix without ambiguity.
Scope
In scope
- Defect analysis and validation (is this actually a defect?)
- ADO Bug work item formatting with all required fields
- Numbered, reproducible repro steps
- Severity and priority assessment with justification
- Root cause hypothesis with labeled confidence
- Evidence collection requirements (screenshots, logs, SOQL, API responses)
- ADO API/MCP defect creation when integration is available and explicitly requested
- Defect categorization across Salesforce metadata types
- Regression and release impact assessment
Out of scope
- Invented severity metrics, SLA percentages, or MTTR without evidence
- Pretending a defect was created in ADO when API call did not succeed
- Duplicating Sprint 7 defect intelligence engine (cross-link instead)
- Full root cause analysis lifecycle (see
quality-intelligence/root-cause-analysis/) - Test case generation (see
skills/ado-test-case-designer/) - Code fixes or Apex/LWC implementation
What ships with it
29 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/experience-cloud-access-error.md 4.3 KB
- examples/integration-api-failure.md 4.7 KB
- examples/README.md 777 B
- examples/salesforce-flow-failure.md 4.4 KB
- knowledge/ado-defect-model.md 3.1 KB
- knowledge/defect-quality.md 2.6 KB
- knowledge/README.md 1017 B
- knowledge/root-cause-analysis.md 3.3 KB
- knowledge/severity-priority-model.md 3.2 KB
- playbooks/defect-logging.md 2.6 KB
- playbooks/defect-reproduction.md 2.1 KB
- playbooks/defect-triage.md 1.9 KB
- playbooks/README.md 793 B
- playbooks/severity-priority-assessment.md 2.2 KB
- prompts/analyze-defect.md 1.2 KB
- prompts/defect-triage.md 973 B
- prompts/generate-ado-defect.md 1.1 KB
- prompts/README.md 735 B
- README.md 3.5 KB
- skill-config.yaml 1.8 KB
- templates/ado-defect-template.md 2.7 KB
- templates/defect-analysis-report.md 2.0 KB
- templates/README.md 662 B
- templates/severity-priority-matrix.md 1.4 KB
- tests/README.md 861 B
- tests/scenario-ado-creation.md 2.2 KB
- tests/scenario-defect-routing.md 1.4 KB
- tests/scenario-repro-quality.md 1.9 KB
- tests/scenario-vague-rejection.md 1.8 KB
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.
- 12d ago First seen · 332 lines · 53 tokens per session scan A 022230cf7809
ado-defect-logger is a skill published in the GitHub repository sudhasubash1990/Salesforce-Enterprise-skills (3 stars, last pushed 24d ago), licensed MIT. It adds 53 tokens to every session and 3,163 once invoked, about $0.0003 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 skills, from other repositories
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
triage-issue
Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket…
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.
investigation
Create an investigation ticket + live-doc for sustained root-cause work (retros, bug archaeology, regression hunts).
browse-flows
Browse Power Automate environments and flows interactively. Use when the user wants to browse, list, or explore their flows and environments.
operating-cadence
Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no…