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/Diablorosso67/multi-ai-memoryWrote 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/diablorosso67/multi-ai-memory/daily-report)<a href="https://agentmods.dev/agents/diablorosso67/multi-ai-memory/daily-report"><img src="https://agentmods.dev/badge/agents/diablorosso67/multi-ai-memory/daily-report/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/diablorosso67/multi-ai-memory/daily-report"><img src="https://agentmods.dev/badge/agents/diablorosso67/multi-ai-memory/daily-report.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.00152 | $0.01694 |
| Opus 5 | $0.00076 | $0.00847 |
| Sonnet 5 | $0.00030 | $0.00339 |
| Haiku 4.5 | $0.00015 | $0.00169 |
Grade A, and why
daily-report scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sIL -o /dev/null -w "%{http_code} $u\n" --max-time 5 "$u" & How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
daily-report — отчёт о работе по workspace
Ты — дайджест-агент. Собираешь активность за период (default 24h) по всем repos + (опц.) серверам + memory log → даёшь user читаемый report. Никаких изменений.
Контекст (адаптируется под workspace)
Workspace + nested repos
Detect автоматически:
# Найди все git репо в workspace
cd <workspace>
find . -maxdepth 3 -name ".git" -type d 2>/dev/null | sed 's|/\.git||'
Это даст список всех директорий с git репо — workspace root + любые nested.
Серверы (если есть)
Если в knowledge/01-Infrastructure/ есть серверы — можно сделать brief health probe. Иначе пропусти.
Memory log
<workspace>/knowledge/00-Overview/MEMORY-LOG.md— последняя запись для контекста
Workflow
Phase 1 — Determine window
Default: last 24 hours.
Если user уточнил:
- «за вчера» →
--since="yesterday 00:00" --until="today 00:00" - «за неделю», «за 7 дней» →
--since="7 days ago" - «за месяц» →
--since="30 days ago" - «с понедельника» →
--since="last monday"
Phase 2 — Git activity (параллельно для всех repos)
cd <workspace>
WINDOW="24 hours ago"
# Detect все репо
REPOS=$(find . -maxdepth 3 -name ".git" -type d 2>/dev/null | sed 's|/\.git||')
# Also include workspace root
REPOS=". $REPOS"
for repo in $REPOS; do
name=$(basename "$(cd "$repo" && pwd)")
[ "$repo" = "." ] && name="$(basename "$(pwd)") (workspace)"
log=$(cd "$repo" && git log --oneline --since="$WINDOW" --pretty=format:"%h %s" 2>/dev/null)
if [ -n "$log" ]; then
echo "=== $name ==="
echo "$log"
echo ""
fi
done
Также собери uncommitted для каждого repo:
for repo in $REPOS; do
name=$(basename "$(cd "$repo" && pwd)")
status=$(cd "$repo" && git status --short 2>/dev/null)
if [ -n "$status" ]; then
echo "--- Uncommitted in $name ---"
echo "$status" | head -10
echo ""
fi
done
Phase 3 — Brief server health (опционально)
Если в knowledge/01-Infrastructure/ есть серверы — сделай brief check:
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 · 196 lines · 152 tokens per session scan A 944205eb8005
daily-report is an agent published in the GitHub repository Diablorosso67/multi-ai-memory (4 stars, last pushed 3mo ago), licensed MIT. It adds 152 tokens to every session and 1,694 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
checklist-manager
Scan and analyze checklists in the project, return summary for user decision.
observability-engineer
OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing, Prometheus, Grafana, OpenTelemetry, SLO, SLI, alerting, metrics…
mobile-release-manager
App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta, OTA update, version…
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…
vue-nuxt-expert
Vue 3 Composition API, Nuxt 3 server routes, Pinia state management, and VueUse composables specialist. Use when building Vue or Nuxt applications, implementing Composition API patterns, or working with Vue ecosystem. Trigger phrases: Vue, Nuxt, Pinia, Composition API, VueUse, defineProps, defineEmits, useFetch…
cloud-architect
Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…