Guardian Agent Runtime
This directory defines the dedicated runtime distribution for helper-backed standalone skills.
Purpose
guardian-agent-runtime is intentionally narrower than the full qip
application package. It exists so target-generic helper-backed skills such as:
guardian-live-browser-explorerguardian-shannon-pentester
can be installed on a fresh machine without shipping the entire QIP backend/API application as the default runtime surface.
Build Model
The wheel is built by scripts/build_agent_runtime_package.py, which stages only
the browser/Shannon helper module closure plus the minimal shared/domain support
files required by those runtimes.
This is an explicit packaging boundary, not a second hand-edited source tree.
Supported Distribution Flows
Local / Manual Install
The recommended human-operated path is a GitLab project deploy token, not a
borrowed OAuth token from glab.
- Create a project deploy token with:
read_package_registryfor installswrite_package_registrytoo if you also want local manual publishes
- Export:
export QIP_AGENT_RUNTIME_GITLAB_PROJECT_ID=79817094
export QIP_AGENT_RUNTIME_REGISTRY_USERNAME=<deploy-token-username>
export QIP_AGENT_RUNTIME_REGISTRY_PASSWORD=<deploy-token-secret>
- Install the helper-backed runtime you need:
python3 scripts/install_helper_backed_skill_runtime.py --skill live-browser-explorer --gitlab-project-id "$QIP_AGENT_RUNTIME_GITLAB_PROJECT_ID"
python3 scripts/install_helper_backed_skill_runtime.py --skill shannon-pentester --gitlab-project-id "$QIP_AGENT_RUNTIME_GITLAB_PROJECT_ID"
If you already have a fully authenticated simple-index URL, the older
QIP_AGENT_RUNTIME_INDEX_URL path still works via:
python3 scripts/install_helper_backed_skill_runtime.py \
--skill live-browser-explorer \
--index-url "$QIP_AGENT_RUNTIME_INDEX_URL"
but it is no longer the preferred operator UX.
Local / Manual Publish
Use the same deploy token, but expose the package-write credential through the publish helper:
export QIP_AGENT_RUNTIME_GITLAB_PROJECT_ID=79817094
export QIP_AGENT_RUNTIME_PUBLISH_USERNAME=<deploy-token-username>
export QIP_AGENT_RUNTIME_DEPLOY_TOKEN=<deploy-token-secret>
python3 scripts/publish_agent_runtime_package.py \
--gitlab-project-id "$QIP_AGENT_RUNTIME_GITLAB_PROJECT_ID" \
--username "$QIP_AGENT_RUNTIME_PUBLISH_USERNAME" \
--password-env QIP_AGENT_RUNTIME_DEPLOY_TOKEN
Automated CI Publish
The long-term automated path is GitLab CI with CI_JOB_TOKEN.
- Root
.gitlab-ci.ymlincludesgitlab-templates/qip-agent-runtime.yml - Set
QIP_AGENT_RUNTIME_PUBLISH=true - Run the
qip:runtime-publishjob onmainor publish automatically on a tag
The CI job resolves the package endpoint from CI_PROJECT_ID and
CI_API_V4_URL and authenticates with gitlab-ci-token plus CI_JOB_TOKEN.
Metadata
Release files for guardian-agent-runtime 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| guardian_agent_runtime-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Release files / guardian_agent_runtime-0.1.0-py3-none-any.whl
| Download URL | guardian_agent_runtime-0.1.0-py3-none-any.whl |
|---|---|
| Size | 80.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
89cf8a0c7a82f854be134a253d49241eb91623c0a6f9ac006cf1ba916d15b732
|
|
BLAKE2b-256 checksum How to use checksums |
f2fd1e60f6975f489127350f0824b6c17523ce749699f120c43671c5b55f7cce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.4 {"installer":{"name":"uv","version":"0.10.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for guardian-agent-runtime 0.1.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.