Skip to main content

SET

Run agentsgen in GitHub Actions, or preview a workflow for your repository before applying it.

CI Release

SET is an optional orchestration layer for agentsgen. Use agentsgen directly if you only need to generate or check AGENTS.md. SET adds workflow presets and reviewable planning exports. No AI runtime or API key is needed for the basic repo-docs workflow.

Quick start

Add .github/workflows/set.yml to your repository:

name: Generate agent docs
on: workflow_dispatch
permissions:
  contents: read
jobs:
  docs:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v5
      - uses: markoblogo/SET@v0.3.1
        with:
          workflow_preset: repo-docs
          path: "."
      - uses: actions/upload-artifact@v4
        with:
          name: proposed-agent-docs
          include-hidden-files: true
          path: |
            AGENTS*.md
            RUNBOOK*.md
            .agentsgen.json
            agents.entrypoints.json
            llms.txt
            docs/ai/

The repo-docs preset runs init, pack, and check using agentsgen v0.5.0. Download and review the artifact before committing it. SET does not commit or push. Existing handwritten files without markers produce generated siblings; a failing check means adoption needs review. For an existing config, set init: "false" when you only want pack generation and validation.

For immutable dependencies, pin SET and agentsgen_ref to reviewed release SHAs. Use the agentsgen PR guard for read-only validation of committed instructions on every PR.

Plan locally, without a central registry

Requires Python 3.10+ and pipx:

pipx install abvx-set==0.3.1

Create .set.json in your repository:

{
  "version": 1,
  "repo": "your-account/your-repo",
  "tools": {
    "agentsgen": {"init": true, "pack": true, "check": true}
  },
  "presets": ["repo-docs"]
}
set-plan-config-apply --config .set.json --repo-root . --format json --export-dir .set-plan

Inspect .set-plan/workflow.set.yml and .set-plan/pr-body.md. The planner exports proposals only; it does not change .github/workflows/ or apply a plan. With no repo arguments, a local .set.json is discovered automatically. Explicit repo names and --all still support the central registry in a source checkout.

Choose a preset

Preset Behavior
minimal Bootstrap docs
repo-docs Init, context pack, validation
site-ai Repo docs plus site analysis; consult advanced requirements

Optional ID hooks, proof artifacts, and capability profiles are described in the advanced guide. Profile exports describe contracts; they do not install runtimes or grant execution permissions.

Compatibility and ownership

Project Responsibility
agentsgen 0.5.0 Detect, generate, preserve handwritten text, validate command references
SET 0.3.1 Choose steps, export plans, invoke the pinned agentsgen version
abvx-agent-skills Optional reusable agent workflows

See integration checks, configuration schema, and contributing. Report reproducible failures with both versions and a redacted minimal .set.json.

Release files for abvx-set 0.3.1

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

Source distribution (sdist)

Source distribution for abvx-set 0.3.1
File Size Uploaded
abvx_set-0.3.1.tar.gz 36.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for abvx-set 0.3.1
File Interpreter ABI Platform
abvx_set-0.3.1-py3-none-any.whl Python 3 none any Details

Total release size: 68.8 kB

Release files / abvx_set-0.3.1.tar.gz

Download URL abvx_set-0.3.1.tar.gz
Size 36.4 kB
Tags Source
SHA-256 checksum
How to use checksums
d66d4cf5115ee3338f11321048838a95a3de432281ccbbef3bbdc2d061eed595
BLAKE2b-256 checksum
How to use checksums
f7d48d5a0d995c7d5fd76491ed92c69543b525634749d45d51c1ccfad2a1f675
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 7, 2026.

Transparency log

Release files / abvx_set-0.3.1-py3-none-any.whl

Download URL abvx_set-0.3.1-py3-none-any.whl
Size 32.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
bd58dbb9d634d88132c1c0523b8b322a8747b0b9c3f233ecdc72d24df3a2095a
BLAKE2b-256 checksum
How to use checksums
871547a4471fedc071f72ccc9503e83d74b63ecac98d8109e09b0c9a1ae8779a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Sep 7, 2026.

Transparency log

Release history Release notifications | RSS feed

0.5.0

2 release files

0.4.0

2 release files

This release

0.3.1 This release

2 release files

0.3.0

2 release files

0.2.4

2 release files

0.2.3

2 release files

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