Pydantic Deep Agents is a self-hosted terminal AI assistant and Python framework for building coding, research, and other AI agents. It gives agents tools such as file access, shell commands, planning, memory, sub-agents, sandboxed execution, and MCP connections, and supports different models.
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 skills add vstorm-co/pydantic-deepagents --skill build-and-compilegit clone --depth 1 https://github.com/vstorm-co/pydantic-deepagentsWrote 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/skills/vstorm-co/pydantic-deepagents/build-and-compile)<a href="https://agentmods.dev/skills/vstorm-co/pydantic-deepagents/build-and-compile"><img src="https://agentmods.dev/badge/skills/vstorm-co/pydantic-deepagents/build-and-compile/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/skills/vstorm-co/pydantic-deepagents/build-and-compile"><img src="https://agentmods.dev/badge/skills/vstorm-co/pydantic-deepagents/build-and-compile.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00015 | $0.00553 |
| Opus 5 | $0.00008 | $0.00277 |
| Sonnet 5 | $0.00003 | $0.00111 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
build-and-compile 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 11d 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.
What it actually says
Build & Compile
Strategies for building code and resolving dependency issues.
Build System Detection
Check for build files in order:
Makefile→make(read it first to understand targets)CMakeLists.txt→cmake -B build && cmake --build buildpyproject.toml/setup.py→pip install -e .package.json→npm install && npm run buildCargo.toml→cargo build --releasego.mod→go build ./...- No build system → compile directly (
gcc,g++,rustc, etc.)
Compilation Strategies
C/C++
- Always read the Makefile/CMakeLists first
- Common flags:
-O2 -Wall -lm -lpthread - Missing headers →
apt-get install lib<name>-dev - Linking errors → check library order (dependencies last:
-lfoo -lbar -lm)
Python
- Use virtual environments when possible
pip install -e .for editable installs- Missing modules → check
requirements.txt,pyproject.toml - Version conflicts → read the actual error, pin versions
Multi-language projects
- Build dependencies first (C libraries before Python bindings)
- Check for Cython, SWIG, or FFI bridges
- Environment variables often needed:
LD_LIBRARY_PATH,PYTHONPATH
Dependency Resolution
- Read the FULL error message — the missing dependency is usually named
- Search for the package:
apt-cache search <name>,pip search <name> - Install the minimum needed — don't install everything
- If a package is unavailable, check for alternatives or build from source
Common Build Failures
| Error | Likely Cause | Fix |
|---|---|---|
fatal error: foo.h: No such file |
Missing dev headers | apt-get install libfoo-dev |
undefined reference to |
Missing library at link time | Add -lfoo flag |
No module named 'foo' |
Missing Python package | pip install foo |
command not found: make |
Build tools missing | apt-get install build-essential |
version 'GLIBC_X.Y' not found |
Binary built for newer system | Rebuild from source |
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.
- 11d ago First seen · 58 lines · 15 tokens per session scan A b46aaa35d5b2
build-and-compile is a skill published in the GitHub repository vstorm-co/pydantic-deepagents (1,061 stars, last pushed 19d ago), licensed MIT. It adds 15 tokens to every session and 553 once invoked, about $0.0001 per session on Opus 5. 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 skills, from other repositories
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
triage-issue
Analyze a GitHub issue, verify claims against the codebase, and close invalid issues with a technical response.
hive.error-recovery
Follow a structured recovery decision tree when tool calls fail instead of blindly retrying or giving up.
skill-repair
Diagnose and fix failing or degraded skills automatically - systemic-first triage, per-category playbooks, and a verification plan.
self-improve
Improve the agent itself, or audit its recent performance - better skills, prompts, workflows, and config, plus a quality/reliability/memory-hygiene review of what it did and what failed.
sonarqube
Operate SonarQube-enabled repositories through the SonarQube CLI (sonar): verify authentication, discover project keys, inspect project metadata, issues, measures, and quality gates, analyze changed code, scan secrets and dependency risks, call authenticated APIs, trigger remediation, configure integrations, and…