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-rfc/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-rfc)<a href="https://agentmods.dev/skills/davidnichols-ops/trustcard/testing-trustcard-rfc"><img src="https://agentmods.dev/badge/skills/davidnichols-ops/trustcard/testing-trustcard-rfc/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-rfc"><img src="https://agentmods.dev/badge/skills/davidnichols-ops/trustcard/testing-trustcard-rfc.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.00025 | $0.00809 |
| Opus 5 | $0.00013 | $0.00404 |
| Sonnet 5 | $0.00005 | $0.00162 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
testing-trustcard-rfc 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing trustcard RFC docs and UI mockups
Use this skill when a PR touches the npm install trust-check RFC or its mockup assets.
Current locations (PR #9 onward):
- RFC:
npm/rfc/0000-package-install-trust-check.md - Mockup:
npm/rfc/assets/trust-check-ui-mockup.html - Logo:
npm/rfc/assets/trustcard-logo.png - Screenshot asset:
npm/rfc/assets/trust-check-ui-mockup.png
Legacy locations (older PRs may still use):
docs/RFC-npm-package-install-attestation.md/docs/rfc-assets/attestation-ui-mockup.htmldocs/RFC-npm-package-install-trust-check.md/docs/rfc-assets/trust-check-ui-mockup.html
Devin Secrets Needed
None. All checks are local.
Environment
- Repo root:
/home/ubuntu/repos/trustcard(or current checkout). - Chrome for Testing is available at
google-chrome. - Node >=18 and
npmare needed to runnpm test.
Quick checks
Render the mockup in Chrome and capture a clean screenshot (replace the path with the PR's mockup location):
google-chrome --no-sandbox --disable-gpu --headless \
--window-size=1280,900 --hide-scrollbars \
--screenshot=/tmp/trust-check-screenshot.png \
"file:///home/ubuntu/repos/trustcard/npm/rfc/assets/trust-check-ui-mockup.html"
Open it in a visible Chrome window for recording:
google-chrome --no-sandbox --disable-gpu --new-window \
"file:///home/ubuntu/repos/trustcard/npm/rfc/assets/trust-check-ui-mockup.html"
Then run the test suite:
cd /home/ubuntu/repos/trustcard
npm test
What to verify
- The rendered page shows
trustcard-logo.pngas the centered hero mark. - The yellow notice explains the zero-config heuristic automation pass and mentions IP/ASN, User-Agent, and the
X-NPM-Trust-Check-Challengeheader. - The primary button reads
Verify with passkey / Touch ID / Windows Hello. - The secondary fallback reads
Email a one-time linkand includes a note that the total flow is two clicks (request + verify in email). - No element or text on the page contains the substring
CAPTCHA. npm testexits 0 with# fail 0.- The RFC markdown contains sections for:
- Heuristic automation pass
- Hardware-bound human trust check
blocked/spam_userclassification (the RFC may useblockedorspam_user; check the PR's term)- Reputation fast pass
- Dead-CAPTCHA rationale (this may be a standalone
## Dead CAPTCHA Rationalesection or a subsection such as### Why visual and cognitive CAPTCHA is not acceptable here)
- CAPTCHA is explicitly deprecated and not recommended as a primary or fallback mechanism.
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 · 77 lines · 25 tokens per session scan A 9b30e48cc0f8
testing-trustcard-rfc is a skill published in the GitHub repository davidnichols-ops/trustcard (4 stars, last pushed 23d ago), licensed MIT. It adds 25 tokens to every session and 809 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-31.
Other skills, from other repositories
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
add-test
Scaffold a test file for an existing tool, resource, or service. Use when the user asks to add tests, improve coverage, or when a definition exists without a matching test file.
harness-design-fuzzing
Reference vocabulary for designing instrumented harnesses that drive vulnerability discovery — design classes (trigger-driven vs coverage-driven), tiered scope (T1 isolated function / T2 multi-component / T3 full build), systematic input exploration, the two-coverage distinction (fuzzer-feedback vs audit)…
email-formatting
Markdown formatting conventions for email summary documents — heading depth, list style, line length, emoji policy, and a mandatory provenance footer. Read this when producing a markdown report that summarizes one or more email messages so the output matches the project's house style.
json-schema-emails
Canonical shape of the .workflow/emails/emails.json file passed between the fetch and summarize states — required fields (sender, recipient, subject, date, body), types, and field semantics. Read this whenever you write or read emails.json so producer and consumer agree on the shape.
test-writing
Write test output, harnesses, and assertions in the terse Unix tradition. Covers Rust #[test], Go testing.T, Python pytest, typed CLI harnesses, and CI integration. Use when writing new tests, test harnesses, CI profiles, or reviewing test output verbosity.