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/promptise-com/foundry/reasoning-patternsgit clone --depth 1 https://github.com/promptise-com/FoundryWhat 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.03531 |
| Opus 5 | $0.00000 | $0.01766 |
| Sonnet 5 | $0.00000 | $0.00706 |
| Haiku 4.5 | $0.00000 | $0.00353 |
Grade A, and why
reasoning-patterns 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 2d 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 — 384 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reasoning Patterns
Every Promptise agent is powered by a Reasoning Graph. By default, build_agent() creates a ReAct graph (single node with tools) — and that default is smart by default: it manages context automatically (context_scope="auto"), so simple tasks are unchanged and deep tool loops stay token-efficient without you choosing anything.
!!! tip "Which one do I need? (most people: none)"
- Just call build_agent(model, servers) — the default handles context and tools well for the overwhelming majority of agents.
- Computing over data (sums, averages, multi-hop joins)? → code-action — write one program instead of chaining tool calls.
- Want a cheap self-check on a weak/cheap model? → verify.
- Need a specific multi-stage shape (debate, research pipeline, deep deliberation)? → the structured patterns below, or build your own graph.
The rest are specialized. Don't reach for a multi-stage pattern expecting more accuracy — on capable models they mostly add latency and tokens; the default plus `code-action` is the efficient path.
You can replace the default with any of the 10 built-in patterns, or build your own.
graph TD
BA[build_agent] -->|'react'| R1[ReAct]
BA -->|'verify'| R9[Verify]
BA -->|'managed'| R10[Managed]
BA -->|'code-action'| R11[Code-Action]
BA -->|'peoatr'| R2[PEOATR]
BA -->|'research'| R3[Research]
BA -->|'autonomous'| R4[Autonomous]
BA -->|'deliberate'| R5[Deliberate]
BA -->|'debate'| R6[Debate]
BA -->|'pipeline'| R7[Pipeline]
BA -->|PromptGraph| R8[Custom]
subgraph Agent Wrapper
M[Memory] --- G[Guardrails] --- C[Cache]
G --- O[Observability] --- E[Events]
end
R1 --> Agent Wrapper
R4 --> Agent Wrapper
R8 --> Agent Wrapper
style BA fill:#1e3a5f,stroke:#60a5fa,color:#fff
style R1 fill:#1a2e1a,stroke:#4ade80,color:#fff
style R9 fill:#1a2e1a,stroke:#4ade80,color:#fff
style R10 fill:#1a2e1a,stroke:#4ade80,color:#fff
style R11 fill:#1a2e1a,stroke:#4ade80,color:#fff
style R2 fill:#2d1b4e,stroke:#c084fc,color:#fff
style R3 fill:#3a2a0a,stroke:#fbbf24,color:#fff
style R4 fill:#3a1a1a,stroke:#f87171,color:#fff
style R5 fill:#2d1b4e,stroke:#c084fc,color:#fff
style R6 fill:#3a1a1a,stroke:#f87171,color:#fff
style R7 fill:#1a2e1a,stroke:#4ade80,color:#fff
style R8 fill:#3a2a0a,stroke:#fbbf24,color:#fff
The Reasoning Graph replaces only the inner loop. All other features (memory, guardrails, cache, observability, events, approval, streaming) stay the same regardless of pattern.
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.
- 2d ago First seen · 384 lines · 0 tokens per session scan A 6c0f2d13cf1b
reasoning-patterns is an agent published in the GitHub repository promptise-com/Foundry (869 stars, last pushed 13d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,531 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-30.
Other agents, from other repositories
lg-react-named-services-config
Agent "lg-react-named-services-config" from kdcube/kdcube, covering lg-react: connecting named services — two config shapes, shape a — per-service connections, shape b — whole surface, choosing and keeping the three declarations honest.
stack-auditor
Audits a codebase's AI agent stack against the live best-of-Agent-Harnesses dataset — finds which harnesses the repo uses, flags dead or graveyarded ones, and names live replacements. Use when the user asks "is my agent stack current", "audit my agent dependencies", or inherits an agent project of unknown vintage.
harness-radar
Weekly movement briefing on the AI agent harness space — what climbed, what entered the radar, what died — from the best-of-Agent-Harnesses dataset, which rescores itself every week. Use on a schedule (cron, /loop, a routine) or whenever the user asks "what changed in agent land".
harness-scout
Picks the right AI agent harness for a described task or project. Use when the user asks "what harness/framework/agent tool should I use", compares agent frameworks, or starts an agent project without a stack decision. Grounded in the live best-of-Agent-Harnesses dataset, never in training-data memory.
agent-orchestration-context-manager
Elite AI context engineering specialist mastering dynamic context management, vector databases, knowledge graphs, and intelligent memory systems. Orchestrates context across multi-agent workflows, enterprise AI systems, and long-running projects with 2024/2025 best practices. Use PROACTIVELY for complex AI…
basic-agents
A basic agent uses a predefined strategy with a simple execution flow that works for most common use cases. It accepts a string input (a question, request, or task description) and sends this input to the configured LLM. The LLM may decide to call provided tools. The agent will execute the tools and send the results…