Borrowing it
Nothing to install: this file belongs to davidnichols-ops/trustcard. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/davidnichols-ops/trustcard/master/.devin/skills/testing-trustcard-behavior/SKILL.mdgit clone --depth 1 https://github.com/davidnichols-ops/trustcardWrote 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/davidnichols-ops/trustcard/testing-trustcard-behavior)<a href="https://agentmods.dev/skills/davidnichols-ops/trustcard/testing-trustcard-behavior"><img src="https://agentmods.dev/badge/skills/davidnichols-ops/trustcard/testing-trustcard-behavior/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/davidnichols-ops/trustcard/testing-trustcard-behavior"><img src="https://agentmods.dev/badge/skills/davidnichols-ops/trustcard/testing-trustcard-behavior.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.00034 | $0.00918 |
| Opus 5 | $0.00017 | $0.00459 |
| Sonnet 5 | $0.00007 | $0.00184 |
| Haiku 4.5 | $0.00003 | $0.00092 |
Grade A, and why
testing-trustcard-behavior 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 9d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing the trustcard behavioral verification engine
Use this skill when you need to verify the lib/behavior.js engine or the mcp-trustcard behavior CLI subcommands on the devin/behavior-engine branch.
Devin Secrets Needed
None. All commands run locally with Node >=18 and the in-repo fixture server.
One-time environment
- Repo root:
/home/ubuntu/repos/trustcard(or the current repo root). - Branch:
devin/behavior-engine. - Node >=18, npm installed, no external dependencies required (
package.jsonhas none). npm testmust pass before claiming behavioral tests are valid.
Commands
Run the full suite:
npm test
Run the behavioral CLI against the benign fixture (process-substitution manifest):
node bin/mcp-trustcard.js behavior \
<(echo '{"server":{"cmd":"node","args":["test/fixtures/behavior-mem-server.js"]}}') \
--corpus /tmp/tc-corpus/benign --json > /tmp/tc-benign.json
# Expected: exit 0, report.summary === "pass"
Run the behavioral CLI against the malicious same-contract fixture:
node bin/mcp-trustcard.js behavior \
<(echo '{"server":{"cmd":"node","args":["test/fixtures/behavior-mem-server.js"],"env":{"TRUSTCARD_EVIL":"1"}}}') \
--corpus /tmp/tc-corpus/evil --json > /tmp/tc-evil.json
# Expected: exit 1, report.summary === "fail",
# findings include prompt_injection, exfiltration_instruction,
# unexpected_tool_behavior, unexpected_network_attempt, all high severity.
Diff the two reports:
node bin/mcp-trustcard.js behavior diff \
/tmp/tc-benign.json /tmp/tc-evil.json --json > /tmp/tc-diff.json
# Expected: exit 1, toolsetDigestMatch === true,
# added findings contain the four classes above.
Isolate a single probe (use --probe <tool>:<type>:<index>):
node bin/mcp-trustcard.js behavior \
<(echo '{"server":{"cmd":"node","args":["test/fixtures/behavior-mem-server.js"]}}') \
--probe greet:valid:0 --json
# Expected: exit 0, probesTotal === 1, probesPassed === 1, summary === "pass".
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.
- 9d ago First seen · 92 lines · 34 tokens per session scan A 2373dc76d23b
testing-trustcard-behavior is a skill published in the GitHub repository davidnichols-ops/trustcard (4 stars, last pushed 20d ago), licensed MIT. It adds 34 tokens to every session and 918 once invoked, about $0.0002 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
atf-testing
Build ServiceNow Automated Test Framework tests and suites — impersonation, form steps, assertions, server-side script steps, test parameters, and execution via snowcreateatftest / snowexecuteatftest.
tabnexus-mcp-evals
Generate, validate, and run isolated Codex-to-TabNexus MCP evaluations with a curated 600-query dataset, executable gold tool labels, safety checks, and best-of-three stability scoring. Use when testing TabNexus MCP tool coverage, Agent behavior, regression quality, destructive-action safety, prompt changes, or a…
blazemeter-private-locations
Comprehensive guide for BlazeMeter Private Locations, including Radar Agent, installation (Docker, Kubernetes, Helm), configuration, management, and troubleshooting. Use when working with Private Locations for (1) Installing agents (Docker, Kubernetes, Helm Chart), (2) Configuring Radar Agent for API Monitoring, (3)…
blazemeter-functional-testing
Comprehensive guide for BlazeMeter Functional Testing, including GUI Functional Tests, API Tests (deprecated), Action Library, and debugging. Use when working with Functional Testing for (1) Creating GUI Functional Tests (YAML, Java IDE, Python IDE), (2) Managing Functional Tests (duplicate, delete, move, rename), (3)…
smoke-test
Post-restart smoke tests + auto-fix for the memex server environment. Walks a fixed check list over the real CLI and MCP surface (status, doctor, search, page round-trip), auto-fixes known issues, and reports what's left.
blazemeter-recorders
Comprehensive guide for BlazeMeter Recorders, including Chrome Extension and Proxy Recorder. Use when working with recorders for (1) Recording tests with Chrome Extension, (2) Creating and using Proxy Recorder, (3) Configuring browsers and devices for proxy recording, (4) Setting port ranges for proxy recorder, or any…