Skip to main content
agents-smith



Contributors Forks Stargazers Issues MIT License Coverage CI Python PyPI

One command to clone AI agent configurations into any project. One command to purge them.


You have used AI coding assistants. You have copied .opencode/, .flowr/, AGENTS.md, and .templates/ into projects by hand — or asked your team to do the same, over and over, across every repository. Files drift out of sync. Versions scatter. Onboarding a new repo means ten minutes of manual file wrangling before the first prompt.

smith enters a project, copies its patterns, and returns something more capable than what it found.

Two commands. No configuration files in your project. No framework overhead. No leftover files after removal.


Who is this for?

Developers — Stop copying AI config files between projects

You set up opencode, flowr, and agent templates in one project. Then you do it again. And again. smith clone pulls the exact same configuration from any GitHub repo, local directory, or URL into your project in one step. smith purge removes every file and every gitignore entry — no orphans, no stale references.

Teams — Consistent agent configurations across every repository

Every team member runs the same smith clone command and gets the same AGENTS.md, the same .opencode agents, the same .flowr workflows. No "it works on my machine." When the template updates, clone again with --overwrite. When a project no longer needs agentic tooling, smith purge and move on.


What it does

smith clone    →  fetches AGENTS.md, .opencode/, .flowr/, .templates/ into your project
smith purge    →  removes every smith-managed file and directory

Safety boundary. Only files matching allowed topics are ever written — regardless of what the source archive contains. Your project never receives arbitrary files.

Clean removal. Purge reads the managed section in .gitignore and deletes exactly what is listed there. The section itself is preserved so you can clone again later.

Source resolution. Three ways to specify where templates come from:

Priority Source Example
1 — CLI flag --source smith clone --source github:myorg/templates
2 — Config [tool.smith] source in pyproject.toml source = "github:myorg/templates"
3 — Default github:nullhack/temple8 Used when no flag or config is set

Quick start

pip install agents-smith
smith clone                                      # default source (temple8)
smith purge                                      # remove everything

That is it. Two commands. No setup, no config file, no framework.


Commands

smith clone

smith clone                                    # default source
smith clone --source github:myorg/templates    # GitHub shorthand
smith clone --source /path/to/local/template    # local directory
smith clone --source https://example.com/t.zip  # URL to archive
smith clone --overwrite                         # replace existing files

Fetches template files from a source, filters by allowed topics, writes them to the project directory, and adds a managed section to .gitignore. Existing files are skipped unless --overwrite is passed.

smith purge

smith purge    # removes all smith-managed files

Reads the smith-managed section in .gitignore and deletes every file and directory listed there. The .gitignore section itself is preserved so you can clone again later.


.gitignore section

# smith managed
AGENTS.md
.opencode/
.flowr/
.templates/
# end smith managed

Only items in this section are removed on purge. Edit it to control what smith manages.


Architecture

smith/
├── cli.py         # CLI — argparse, subcommands (clone, purge)
├── core.py        # Domain — resolve_source, fetch, clone, purge, FileSpec
└── gitignore.py   # Infrastructure — .gitignore section management

Flat module structure. Two commands. No framework overhead.


License

MIT — see LICENSE.

Author: @nullhack · Documentation

Metadata

Release files for agents-smith 1.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for agents-smith 1.0.0
File Size Uploaded Provenance Actions
agents_smith-1.0.0.tar.gz 10.8 kB With provenance Details for agents_smith-1.0.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for agents-smith 1.0.0
File Interpreter ABI Platform Actions
agents_smith-1.0.0-py3-none-any.whl Python 3 none any Details for agents_smith-1.0.0-py3-none-any.whl

Total release size: 20.9 kB

Release files / agents_smith-1.0.0.tar.gz

Download URL agents_smith-1.0.0.tar.gz
Size 10.8 kB
Tags Source
SHA-256 checksum
How to use checksums
f53f27d767fae974f27663a2f6702546dcfaf1da92282cb2428f5041abd4bc0a
BLAKE2b-256 checksum
How to use checksums
5e59eb40b30f1bfe96e4890a5cff457e10270073744d870cae2726d5ab4d7068
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on May 2, 2026.

Transparency log

Release files / agents_smith-1.0.0-py3-none-any.whl

Download URL agents_smith-1.0.0-py3-none-any.whl
Size 10.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c2e051f20d368c420efa865b73890407726189047ab9155bf7bd89a59ef5d8d1
BLAKE2b-256 checksum
How to use checksums
7bf8e5ba7318a95a29b732c7822e7b4a8eecbb25b8b6a0b1484d48afaa437d12
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on May 2, 2026.

Transparency log

Security for agents-smith 1.0.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for agents_smith-1.0.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on May 2, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page