Borrowing it
Nothing to install: this file belongs to nickna/Conduit. 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/nickna/Conduit/master/AGENTS.mdgit clone --depth 1 https://github.com/nickna/ConduitWrote 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/instructions/nickna/conduit/agents-md)<a href="https://agentmods.dev/instructions/nickna/conduit/agents-md"><img src="https://agentmods.dev/badge/instructions/nickna/conduit/agents-md.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.1 | $0.05437 | $0.05437 |
| Opus 5 | $0.02719 | $0.02719 |
| Sonnet 5 | $0.01087 | $0.01087 |
| Haiku 4.5 | $0.00544 | $0.00544 |
Grade A, and why
Conduit AGENTS.md 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST http://localhost:5002/api/virtual-keys \ How it starts
The opening of the file, as written. The whole thing — 900 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agents Guide
Last Updated: 2025-11-25
Comprehensive guide for building and deploying AI agents using ConduitLLM's agentic workflows and function calling capabilities.
Table of Contents
- Overview
- Agent Architecture
- Configuration
- Building Agents
- Deployment & Operations
- Examples & Templates
- Advanced Features
- Troubleshooting
- Related Documentation
Overview
What are Agents in ConduitLLM?
In ConduitLLM, agents are AI systems that can autonomously execute functions and tools to accomplish complex tasks. Unlike simple chat completions, agents can:
- Make decisions about when to call functions
- Execute multiple functions in a single workflow
- Handle dependencies between function calls
- Iterate on results until a task is complete
- Provide real-time feedback during execution
Agentic Mode vs Manual Function Calling
ConduitLLM supports two approaches to function calling:
Manual Function Calling
- Your application receives
tool_callsfrom the LLM - You decide which functions to execute and how
- You control the flow and iteration logic
- Full control but more complex implementation
Agentic Mode (Recommended for Agents)
- Conduit automatically executes requested functions
- Handles dependency detection and parallel/sequential execution
- Manages iteration limits and cost tracking
- Provides real-time streaming events for progress
- Simplifies agent development significantly
Use Cases
Agents are ideal for:
- Data analysis workflows (query databases, process results, generate reports)
- API integration (call external services, transform data, take actions)
- Content creation pipelines (research, draft, edit, publish)
- Customer service automation (lookup records, take actions, respond)
- Development assistants (read code, run tests, suggest fixes)
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 · 900 lines · 5,437 tokens per session scan A e0c2c9d312b4
Conduit AGENTS.md is an instructions file published in the GitHub repository nickna/Conduit (10 stars, last pushed 9d ago), licensed MIT. It adds 5,437 tokens to every session, about $0.0272 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-09-04.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.