Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add synaptiai/synapti-marketplace/plugin install dossierWrote 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/commands/synaptiai/synapti-marketplace/claim)<a href="https://agentmods.dev/commands/synaptiai/synapti-marketplace/claim"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/claim/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/commands/synaptiai/synapti-marketplace/claim"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/claim.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.00044 | $0.01847 |
| Opus 5.5 | $0.00018 | $0.00739 |
| Sonnet 5.5 | $0.00009 | $0.00369 |
| Haiku 4.5 | $0.00004 | $0.00185 |
Grade A, and why
claim 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 1mo 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adjudicate Claim: $ARGUMENTS
One question: can this sentence be said externally, and if so, in exactly what words?
Required Skills
disclosure-gating— the claim register, the approval boundary, and the derivation rulesevidence-ledger— trace the claim to its rows and read the claim state
References
Phase 0 — Resolve
_RAW="$ARGUMENTS"
printf '%s\n' "### Claim Arguments"
printf '%s\n' "ARGS=$_RAW"
__dr="${CLAUDE_PLUGIN_ROOT:-}"
[ -x "$__dr/bin/dossier-claim-scan.sh" ] || __dr=$({ printf '%s\n' plugins/dossier; ls -d "$HOME"/.claude/plugins/cache/synapti-marketplace/dossier/*/ 2>/dev/null | sort -Vr; printf '%s\n' "$HOME/.claude/plugins/marketplaces/synapti-marketplace/plugins/dossier"; } | while read -r __p; do [ -x "${__p%/}/bin/dossier-claim-scan.sh" ] && { printf '%s\n' "${__p%/}"; break; }; done)
printf '%s\n' "### Preflight"
if [ ! -x "$__dr/bin/dossier-claim-scan.sh" ]; then
printf '%s\n' "CLAIM_STATE=blocked"
printf '%s\n' "CLAIM_ERROR=dossier plugin scripts not found — reinstall or upgrade the plugin"
true; exit 0
fi
OUTPUT_ROOT=$("$__dr/bin/dossier-resolve-config.sh" --default "docs/dossier" dossier.project.outputRoot 2>/dev/null)
printf '%s\n' "OUTPUT_ROOT=$OUTPUT_ROOT"
printf '%s\n' "DISCLOSURE_POLICY=$("$__dr/bin/dossier-resolve-config.sh" --default internal-only dossier.disclosure.policy 2>/dev/null)"
printf '%s\n' "APPROVAL_REQUIRED=$("$__dr/bin/dossier-resolve-config.sh" --default required dossier.disclosure.publicClaimApproval 2>/dev/null)"
printf '%s\n' "REGISTER_EXISTS=$([ -f "$OUTPUT_ROOT/00-control/claim-and-disclosure-register.md" ] && printf '%s\n' true || printf '%s\n' false)"
printf '%s\n' "LEDGER_EXISTS=$([ -f "$OUTPUT_ROOT/00-control/evidence-ledger.md" ] && printf '%s\n' true || printf '%s\n' false)"
true
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.
- 1mo ago Changed 3187c7b6197a
- 1mo ago First seen · 132 lines · 44 tokens per session scan A b9284344ea06
claim is a command published in the GitHub repository synaptiai/synapti-marketplace (7 stars, last pushed 10d ago), licensed Apache-2.0. It adds 44 tokens to every session and 1,847 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other commands, from other repositories
alcoa-guard
Lint a record / dataset / kit run for ALCOA+ data integrity (attribution, contemporaneity, completeness, accuracy, consistency). Deterministic findings + a human-judgment checklist; the report is a DRAFT, the human owns the verdict.
create-worktree
Follow these steps to create a git worktree.
patent-check
Check environment readiness in the active host before first RESEARCH or project resume.
dpia
Data Protection Impact Assessment (DPIA) guidance and execution.
paper-trail-ingest
Ingest the citations of one SOTA into the registry. Extracts bibliographic sections, parses citations via the citation-parser sub-agent, resolves DOI via Crossref/S2, deduplicates against the registry, creates new candidate refs, and substitutes free-text citations with [[wikilinks]]. Required first step to make a…
audit-setup
Generate security audit logging system with immutable event trail, compliance reporting (GDPR/SOC2), and suspicious activity alerting. Usage: /audit-setup [init | report | alerts | compliance].