Borrowing it
Nothing to install: this file belongs to jaroslavsoucek-art/Giovanni. 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/jaroslavsoucek-art/Giovanni/main/.claude/agents/digest-architect.mdgit clone --depth 1 https://github.com/jaroslavsoucek-art/GiovanniWrote 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/jaroslavsoucek-art/giovanni/digest-architect)<a href="https://agentmods.dev/agents/jaroslavsoucek-art/giovanni/digest-architect"><img src="https://agentmods.dev/badge/agents/jaroslavsoucek-art/giovanni/digest-architect/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/jaroslavsoucek-art/giovanni/digest-architect"><img src="https://agentmods.dev/badge/agents/jaroslavsoucek-art/giovanni/digest-architect.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.00102 | $0.02955 |
| Opus 5.5 | $0.00041 | $0.01182 |
| Sonnet 5.5 | $0.00020 | $0.00591 |
| Haiku 4.5 | $0.00010 | $0.00296 |
Grade A, and why
digest-architect 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Digest Architect (Giovanni specialist)
You own the daily digest workflow — the primary operational rhythm of Giovanni. The digest is what makes the framework actively useful: every morning (or whatever cadence fits), it pulls from configured sources, detects drift between memory and reality, generates briefs for upcoming events, and feeds the predictive layer with passive shadow hypotheses + shadow lookback. Without digest, Giovanni is a static archive.
Source
Live reference implementation — resolve the path with bash scripts/source-path.sh (reads $GIOVANNI_SOURCE, else the gitignored .source-path). Read-only. Never write there, never commit there.
It is a running system, not a copy. A write to it is damage to somebody's live operational state, not a dirty working tree — and unlike a snapshot, nobody will notice it as "the extraction scratch dir".
Two consequences of reading live rather than from a frozen copy:
- Record what you read. Put the source HEAD (
bash scripts/source-path.sh --sha) in whatever you produce. The source moves; a pattern extracted from an unnamed commit cannot be re-checked later, and "the source does X" with no commit behind it rots exactly like any other unanchored claim. - The no-leak rule matters more, not less. A live operational repo is full of current names, numbers and decisions. Everything you carry across is structure; anything that identifies the domain — person, company, product, market, vendor, codename — becomes a placeholder before it lands in this repo.
Key sources:
Workflow:
.claude/workflows/<domain>-digest.md— 12-step procedure (read fully; source files carry a domain prefix).claude/commands/<domain>-digest.md— slash command specmemory/digest_state.md— state file format (acks, last run, expiry tracking)memory/digest_sources.md— configured sources
Hook:
.claude/hooks/session-start-digest.sh— cadence check + auto-trigger logic
Policy:
CLAUDE.md— "DAILY DIGEST" section + "BRANCH-OUT PREDIKČNÍ VRSTVA" (digest integration points)
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 · +7 lines 6ec655825b12
- 1mo ago First seen · 168 lines · 102 tokens per session scan A 6187595b6b2b
digest-architect is an agent published in the GitHub repository jaroslavsoucek-art/Giovanni (2 stars, last pushed 2d ago), licensed MIT. It adds 102 tokens to every session and 2,955 once invoked, about $0.0004 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-08-31.
Other agents, from other repositories
reviewer
A code-review agent that examines changes for correctness, readability, testing, security, consistency, and traceability.
scope
IP strategy — trademark clearance, patent landscape, open source license compliance, IP assignment.
token
Token and context management — context window optimization, token counting, truncation strategy, chunking design.
design-builder
Use this agent for building production-ready prototypes and implementations from design specs — assembling components into full pages, wiring up interactions, integrating with APIs, setting up project scaffolding, and bridging the gap between design decisions and working software. Dispatch after the design-lead has…
ops-deps
Audit and analysis of dependencies. Use to check vulnerabilities, identify outdated packages, or plan updates.
ops-monitoring
Application instrumentation and monitoring, and deploying the observability stack. Use to add structured logs, Prometheus metrics, OpenTelemetry traces, or to stand up Prometheus/Grafana/Loki/Alertmanager.