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/usethefork/synapse/indexgit clone --depth 1 https://github.com/UseTheFork/synapseWhat 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.00353 |
| Opus 5 | $0.00000 | $0.00177 |
| Sonnet 5 | $0.00000 | $0.00071 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
index 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 yesterday.
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.
What it actually says
Agents
Agents are the core of the Synapse library. Every component, such as Tools, Memory, or OutputSchema, must be attached to an agent.
Getting Started
It's recommended to define a standard location for your Agents. In Laravel, a good practice is to place them inside the App/Agents directory.
Create a new class that extends the abstract Agent class.
You will need to define a few methods, interfaces, and variables:
$promptView: The Blade view that the agent uses as its prompt template. See the Prompts section for more details.HasIntegration: This interface tells the agent to look for theresolveIntegrationmethod when booting. See the Integrations section for more details.resolveIntegration: The API connection the agent should use when invoked. See the Integrations section for more details.
[!TIP] If you set a default integration in your config file, you do not need to add the
resolveIntegrationmethod or theHasIntegrationinterface to your agent.
<?php
use UseTheFork\Synapse\Agent;
use UseTheFork\Synapse\Contracts\Integration;
use UseTheFork\Synapse\Integrations\OpenAIIntegration;
use UseTheFork\Synapse\Contracts\Agent\HasIntegration;
class SimpleAgent extends Agent implements HasIntegration
{
protected string $promptView = 'synapse::Prompts.SimplePrompt';
public function resolveIntegration(): Integration
{
return new OpenAIIntegration;
}
}
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.
- yesterday First seen · 38 lines · 0 tokens per session scan A 30f30bcbc382
index is an agent published in the GitHub repository UseTheFork/synapse (50 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 353 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
planner
Use this agent when the user needs a detailed implementation plan for a complex feature or task. Triggers on multi-step features, refactoring efforts, or tasks with unclear scope. Context: User starting a complex feature user: "I need to implement experiment comparison functionality" assistant: "I'll use the planner…
journey-synthesizer
Derives the run's journey map from the project profile and diff classification. This is the runtime replacement for v2's static journey catalog — there is no baked-in journey list. Every journey in the output traces to a real touched surface in the diff.
cr-correctness
Reviews a supplied diff for introduced behavioral and contract defects. Use only when dispatched by the code-review skill.
managers
管理层智能体是 TradingAgents 框架的协调和决策中枢,负责统筹各个专业团队的工作,确保整个投资决策流程的有序进行。管理层包括研究经理和风险经理,分别负责研究活动的协调和风险管理的统筹。.
analysts
制造业分析师团队是系统的核心信息收集和分析单元,由4个专业化智能体组成,专注于从不同维度收集和分析影响制造业补货决策的外部信息。.
database
Database schema, Eloquent models, and migrations.