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 skills/microsoft/accordant/troubleshootingnpx skills add microsoft/accordant --skill troubleshootinggit clone --depth 1 https://github.com/microsoft/accordantWrote 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/microsoft/accordant/troubleshooting)<a href="https://agentmods.dev/skills/microsoft/accordant/troubleshooting"><img src="https://agentmods.dev/badge/skills/microsoft/accordant/troubleshooting.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.02586 |
| Opus 5 | $0.00015 | $0.01293 |
| Sonnet 5 | $0.00006 | $0.00517 |
| Haiku 4.5 | $0.00003 | $0.00259 |
Grade A, and why
accordant-troubleshooting 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 — 402 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Troubleshooting Accordant
This skill covers common mistakes, debugging techniques, and how to fix typical issues.
Test Failures
"No matching expected outcome"
The response doesn't match any Expect.That() predicate.
Diagnosis:
// Check what the spec expects vs what you got
var (isValid, message, _) = spec.Allows(operation, request, actualResponse, stateProfile);
Console.WriteLine(message); // Shows which expectation failed and why
Common causes:
- Predicate too strict: Response has extra fields or slightly different values
- Wrong state: The spec thinks it's in state A, but the system is in state B
- Missing error case: You didn't handle an error condition in Apply
Fix:
// Add explanation to predicates for better debugging
Expect.That<ApiResult<User>>(
r => r.IsSuccess && r.Data.Name == expectedName,
$"Expected success with name '{expectedName}', got status={r?.StatusCode}, name='{r?.Data?.Name}'")
"State mismatch after operation"
Tracked state diverges from actual system state.
Common causes:
- Forgot to reset state: Previous test left data behind
- Missing ThenState: Operation modifies state but spec uses
.SameState() - Wrong state update: ThenState modifies wrong fields
Fix:
// Ensure BeforeEachAsync properly resets
var results = await spec.RunTests(context, initialState, testCases, new TestExecutionOptions
{
BeforeEachAsync = async _ =>
{
// Actually verify reset worked
await client.DeleteAll();
var count = await client.GetCount();
if (count != 0) throw new Exception("Reset failed!");
}
});
Tests Pass Individually, Fail in Sequence
Common causes:
- Shared mutable state in test fixtures
- Incomplete reset between tests
- Timing issues with async operations
Fix:
// Create fresh client for each test
var results = await spec.RunTests(context, initialState, testCases, new TestExecutionOptions
{
BeforeEachAsync = async ctx =>
{
// Fresh client, fresh start
var httpClient = _factory.CreateClient();
ctx.Context.Register(new ApiClient(httpClient));
await ResetDatabase();
}
});
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 · 402 lines · 29 tokens per session scan A 45bb06b778fa
accordant-troubleshooting is a skill published in the GitHub repository microsoft/accordant (58 stars, last pushed 16d ago), licensed MIT. It adds 29 tokens to every session and 2,586 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.
Other skills, from other repositories
keploy-docs
Guide for contributing to the Keploy documentation site at github.com/keploy/docs. Invoke when a change in keploy/keploy introduces, removes, or alters user-visible behavior (new CLI flag, changed default, new command, new configuration field, new on-disk format) and the docs need to catch up — or when the user asks…
keploy-pr-workflow
Guide for creating PRs and issues on keploy repositories — PR format, customer-data hygiene, commit conventions, sign-off. Invoke when the user asks to open, update, or review a pull request or issue, when preparing a commit that will land in main, or whenever a change is about to leave the local machine.
keploy-e2e-test
End-to-end verification of a change to keploy/keploy using keploy's own record/replay against a real sample application. Use whenever the user asks to test a change, verify a fix, prove that a modification works in practice, add e2e coverage for a PR, reproduce a bug against a sample app, or wire a behavior into CI.…
implementing-api-security-testing-with-42crunch
Implement comprehensive API security testing using the 42Crunch platform to perform static audit and dynamic conformance scanning of OpenAPI specifications.
API Test Suite Generator
Automatically generate comprehensive API test suites from OpenAPI specifications covering CRUD operations, error handling, authentication, pagination, and edge cases.
AI Test Generation Patterns
Systematic patterns for prompting AI coding agents to generate high-quality tests including prompt engineering for test creation, coverage-driven generation, mutation-aware testing, and review checklists for AI-generated test code.