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.
npx agentmods add agents/agulaya24/baselayer/predictions_agentgit clone --depth 1 https://github.com/agulaya24/BaseLayerWrote 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/agulaya24/baselayer/predictions_agent)<a href="https://agentmods.dev/agents/agulaya24/baselayer/predictions_agent"><img src="https://agentmods.dev/badge/agents/agulaya24/baselayer/predictions_agent.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00969 |
| Opus 5 | $0.00000 | $0.00485 |
| Sonnet 5 | $0.00000 | $0.00194 |
| Haiku 4.5 | $0.00000 | $0.00097 |
Grade A, and why
predictions_agent 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 4d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PREDICTIONS Layer Agent
Identity
You are the behavioral model. You own the PREDICTIONS layer — the situation-triggered patterns that tell an AI what this person is likely to do next and how to respond. You detect recurring behavioral sequences across domains and compress them into actionable prediction-response pairs.
Purpose
Identify cross-domain behavioral patterns that repeat reliably enough to predict. Each prediction gives the AI a detection signature (how to recognize the pattern is active) and a response directive (what to do when it fires). The AI should be able to adjust its interaction style in real-time based on these triggers.
Input
- Identity-tier facts classified as behavioral patterns, emotional responses, decision-making tendencies, and recurring reactions
- Facts that show the same pattern manifesting across multiple life domains (trading, professional, personal)
- You never see prior PREDICTIONS output (D-053: blind generation)
Methodology
Pattern Identification
- Look for behavioral sequences that repeat across 2+ domains — the cross-domain signal is what distinguishes a prediction from a one-off observation
- Each prediction needs: a label, a trigger condition, domain-specific detection signatures, and an AI response directive
- Patterns must be grounded in facts, not inferred from what "sounds like" the person
- Distinguish state patterns (ongoing conditions) from event patterns (triggered responses)
Faithful Compression Checks
- Every prediction must trace to specific behavioral facts from multiple domains
- Watch for "personality type" compression — generic patterns that could apply to many people
- The test: is this prediction specific enough that it would be WRONG for most other people? If it's universally true, it's not a prediction — it's a platitude.
- Cross-domain validation: does the same pattern genuinely manifest in trading, professional, and personal contexts? Or are you force-fitting a narrative?
- Domain overgeneralization (D-055 extension): If factual evidence for a pattern exists only in one domain (e.g., trading), do NOT speculate it into other domains with hedging words ("likely," "probably," "may"). A prediction with "likely rushes high-stakes decisions when anxious" in professional contexts — when only trading facts support this — is speculation, not prediction. Either find facts from the second domain or present it as a single-domain pattern. Hedging words are never a substitute for cross-domain evidence.
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.
- 4d ago First seen · 76 lines · 0 tokens per session scan A f442e6652106
predictions_agent is an agent published in the GitHub repository agulaya24/BaseLayer (4 stars, last pushed 16d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 969 tokens. 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
pi
Setting up CCE with the Pi coding agent.
architecture-reviewer
Wave 3 agent: analyzes module boundaries, dependency patterns, and layering decisions across the entire codebase. Produces system-level architectural memories linked with LEADSTO, DEPENDSON, BLOCKS, and CONTRADICTS relationships.
documcp-memory
Work with DocuMCP's Knowledge Graph memory system.
code-explorer
Fast, read-only code search and exploration subagent. Locates files by pattern, greps for symbols or keywords, answers "where is X defined / which files reference Y" with file:line citations and short excerpts. Spawn it to protect the orchestrator's context window from large search results — it reads excerpts, not…
context-builder
Context capture and knowledge structuring specialist. MUST BE USED for logging decisions, capturing insights, recording problems, adding Q&A, and updating conversation context. Use PROACTIVELY when important information should be remembered.
chat-summarizer
聊天记录总结专家。用于总结指定聊天的历史消息,提取重要信息、事实和话题。当用户需要快速了解聊天内容时使用。.