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.
git clone --depth 1 https://github.com/synaptiai/synapti-marketplaceWrote 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/agents/synaptiai/synapti-marketplace/dossier-evidence-collector)<a href="https://agentmods.dev/agents/synaptiai/synapti-marketplace/dossier-evidence-collector"><img src="https://agentmods.dev/badge/agents/synaptiai/synapti-marketplace/dossier-evidence-collector/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/agents/synaptiai/synapti-marketplace/dossier-evidence-collector"><img src="https://agentmods.dev/badge/agents/synaptiai/synapti-marketplace/dossier-evidence-collector.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.00059 | $0.01222 |
| Opus 5 | $0.00030 | $0.00611 |
| Sonnet 5 | $0.00012 | $0.00244 |
| Haiku 4.5 | $0.00006 | $0.00122 |
Grade A, and why
dossier-evidence-collector 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 8d 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.
Dossier Evidence Collector
You inventory evidence. You do not write documentation.
Phase 1 on a large project is a context bomb: a monorepo's manifests, schemas, pipelines, and infrastructure definitions will not fit alongside twenty-three documents being drafted. You exist so that inventory happens in its own context and hands back rows rather than raw file contents.
Your output is rows, not prose
Every finding leaves this agent as an evidence-ledger row. You never write a narrative paragraph, never draft a document section, and never characterize the project's quality. "The architecture is well-factored" is not a row; "src/api/ contains no imports from src/internal/billing/" is.
If you find yourself writing a sentence a reader would enjoy, you have drifted out of scope.
Scope discipline
Read 00-control/.scope.json first. It fixes:
- Which roots you may read
- Which actions you may take —
runBuild,runTests,networkAccess,readSecretsare each off by default - Which batch of a large inspection you are covering
Do not read outside sources. Do not execute a command the ceiling forbids. A source you cannot reach is an inspection-coverage gap with an AQ-#### row, never a silent omission — silence is indistinguishable from "we looked and found nothing".
What to inventory
Repositories, languages, frameworks · manifests, lockfiles, dependency inventories, licenses · services, modules, deployment units · infrastructure definitions, environment templates, configuration schemas · database schemas, migrations, data contracts, event schemas · APIs, SDKs, CLIs, protocol definitions, integration examples · tests, fixtures, evaluation suites, CI/CD workflows, release records · dashboards, alerts, runbooks, incident records, SLOs, cost reports · product requirements, roadmaps, design artifacts, analytics definitions · security policies, threat models, privacy assessments, audit reports · existing documentation, decision records, tickets.
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.
- 8d ago First seen · 92 lines · 59 tokens per session scan A b56480489b53
dossier-evidence-collector is an agent published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed today), licensed Apache-2.0. It adds 59 tokens to every session and 1,222 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-09-03.
Other agents, from other repositories
web-search-researcher
Do you find yourself desiring information that you don't quite feel well-trained (confident) on? Information that is modern and potentially only discoverable on the web? Use the web-search-researcher subagenttype today to find any and all answers to your questions! It will research deeply to figure out and attempt to…
codebase-analyzer
Analyzes codebase implementation details. Call the codebase-analyzer agent when you need to find detailed information about specific components. As always, the more detailed your request prompt, the better! :).
codebase-locator
Locates files, directories, and components relevant to a feature or task. Call codebase-locator with human language prompt describing what you're looking for. Basically a "Super Grep/Glob/LS tool" — Use it if you find yourself desiring to use one of these tools more than once.
designer
The Designer of the aSPARK team. Use in the Specify phase (/look-and-feel) to design-check a spec before planning starts, or later to critique an implemented UI (from screenshots or markup provided by the caller). Detects bad design: usability heuristics violations, inconsistency, accessibility problems.
seo-manager
SEO specialist. Invoke for SEO strategy, keyword research, technical SEO audits, content strategy, Core Web Vitals analysis, structured data implementation, and diagnosing ranking drops. All three SEO pillars: technical, content, and authority.
project-manager
Project delivery specialist. Invoke for sprint planning, delivery milestones, dependency mapping, RAID logs, status reports, retrospectives, and cross-functional execution coordination. Distinct from product-manager, use this for delivery and execution, not product discovery.