This project has been quarantined by PyPI admins. It cannot be installed or modified until a security review is complete.
AGA · Agent Governance & Assurance
Secure your Skills. Guard your Agents.
AGA is an open-source security scanner for AI Agent Skills. Think of it as npm audit for the Agent ecosystem — catch malicious or high-risk Skills before they reach production.
✨ What AGA Does
- 🔍 Scans local Skill directories (
SKILL.md+scripts/) - 🛡️ Detects Code Injection (CI), Prompt Injection (PI), and MIXED attacks
- 📊 Analyzes intent-behavior alignment ("does the code do what the docs say?")
- 📈 Assigns a risk score (0–100), attack labels (B1–B15), and remediation suggestions
- 🔗 Integrates with GitHub Actions / CI/CD pipelines
AGA's detection taxonomy is aligned with the MalSkillBench research benchmark, covering 15 malicious behavior categories across 3 attack vectors.
🚀 Quick Start
Installation
pip install aga-sec
Scan a Skill
aga scan ./my-skill
Example output:
🔍 AGA Scan Report: my-skill
────────────────────────────────────────
Risk Score: 78/100 ⚠️
Risk Level: HIGH
Attack Type: MIXED
📋 Issues Found:
🔴 [PI] B12 (confidence: 0.82)
Instruction override detected in SKILL.md
🔴 [CI] B3 (confidence: 0.76)
Remote code execution pattern in scripts/main.py
💡 Suggestions:
1. Review SKILL.md for instruction override patterns
2. Never download and execute remote code
3. Add explicit permission declarations
❌ Status: FAILED
Deep Scan (with LLM)
aga scan ./my-skill --deep
Uses an LLM to analyze semantic intent-alignment and detect subtle prompt injections.
CI Mode
aga scan ./my-skill --ci # exit code 0 = pass, 1 = fail
JSON Output
aga scan ./my-skill --json
🧠 Design
AGA uses a dual-engine architecture:
| Engine | Type | What it cathes |
|---|---|---|
| Rule Engine | Deterministic pattern matching | Known malicious patterns, unsafe code, credential theft |
Semantic Engine (--deep) |
LLM-powered analysis | Intent-behavior misalignment, subtle prompt injection |
The Rule Engine runs on every scan (zero cost, sub-second). The Semantic Engine is opt-in for deeper analysis.
🧩 Command Reference
| Command | Description |
|---|---|
aga scan <path> |
Scan a skill directory |
aga scan --deep <path> |
Deep scan with LLM analysis |
aga scan --json <path> |
JSON output for tool consumption |
aga scan --ci <path> |
CI mode (exit code driven) |
aga rule list |
List loaded detection rules |
aga rule pull |
Pull latest community rules |
aga bench run |
Run MalSkillBench benchmark |
aga config show |
Show current configuration |
aga data pull |
Download benchmark datasets |
📦 SDK Usage
from aga import Analyzer
analyzer = Analyzer()
# Single scan
report = analyzer.scan("./my-skill")
print(f"Risk: {report.risk_score}/100 ({report.risk_level})")
# Batch scan
reports = analyzer.batch_scan(["./skill-a", "./skill-b"])
for r in sorted(reports, key=lambda r: r.risk_score, reverse=True):
print(f"{r.skill_name}: {r.risk_score}")
📊 Benchmark (7,891 Skills · 16 Rules · Dual Engine)
Full-scale (MalSkillBench entire dataset)
| Metric | Score |
|---|---|
| Precision | 66.2% |
| Recall | 81.1% |
| F1 Score | 72.9% |
| Accuracy | 70.2% |
| Skills scanned | 7,891 (3,898 malware + 3,993 benign) |
| Scan time | 523s (15 skills/s, streaming from git, single-threaded) |
Curated subset (50 labeled skills)
| Metric | Score |
|---|---|
| Precision | 78.1% |
| Recall | 100.0% |
| F1 Score | 87.7% |
Per-behavior recall (full dataset, 16 rules)
| B1: 43.9% | B2: 17.7% | B3: 77.6% | B4: 72.4% | B5: 99.2% | | B6: 92.8% | B7: 77.2% | B8: 85.1% | B9: 52.3% | B10: 33.3% | | B11: 71.4% | B12: 20.8% | B13: 38.9% | B14: 6.9% | B15: 29.3% |
Key insight: CI behaviors (B1-B9, avg 70.5%) are significantly easier for rule engines than PI behaviors (B10-B15, avg 33.4%). B14 (Goal Hijacking, 6.9%) is purely semantic — effectively invisible to static analysis. The --deep semantic engine (DeepSeek-powered) is essential for PI coverage.
Run the benchmark yourself:
aga data pull malskillbench
aga bench run
🗺 Roadmap
- Project scaffolding and CLI skeleton (
aga scanworks end-to-end) - Rule Engine with 15 built-in rules (B1–B15 full coverage)
- MalSkillBench benchmark suite (50-skills, precision/recall tracked)
-
--deepLLM semantic analysis (Phase 2) - Docker sandbox runtime verification (Phase 3)
- Web Dashboard & enterprise policy center
🔬 Research Alignment
AGA's risk taxonomy maps to the MalSkillBench three-dimensional attack space:
| Vector | Behaviors | Detection | Status |
|---|---|---|---|
| CI (Code Injection) | B1–B9 | Rule Engine + AST analysis | 77.3% precision |
| PI (Prompt Injection) | B10–B15 | Rule Engine + instruction analysis | Requires --deep for B14/B15 |
| MIXED | B1–B9 coordinated | Dual-engine joint analysis | Rule engine detects CI component |
🤝 Contributing
AGA is open source (Apache 2.0) and community-driven. The easiest way to contribute:
- Write a detection rule (just a YAML file!) —
aga rule contribute - Report a false positive or missed detection
- Improve the parser for new skill formats
See CONTRIBUTING.md for details.
📄 License
Apache 2.0 — see LICENSE for full text.
📚 Citation & Attribution
AGA's behavior taxonomy (B1-B15) is derived from MalSkillBench. If you use AGA in research, please cite:
@misc{guo2026malskillbench,
title={MalSkillBench: A Runtime-Verified Benchmark of Malicious Agent Skills},
author={Wenbo Guo and Wei Zeng and Chengwei Liu and Xiaojun Jia and
Yijia Xu and Lei Tang and Yong Fang and Yang Liu},
year={2026},
eprint={2606.07131},
archivePrefix={arXiv},
primaryClass={cs.CR},
}
See ATTRIBUTION.md for full attribution details.
AGA · Secure your Skills. Guard your Agents.
Metadata
Release files for aga-sec 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Loss of provenance
These files do not have provenance metadata, despite files in a prior release including this data.
We recommend further investigation before installing these files. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| aga_sec-0.1.2.tar.gz | 133.2 kB | Without provenance | Details for aga_sec-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aga_sec-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for aga_sec-0.1.2-py3-none-any.whl |
Total release size: 187.4 kB
Release files / aga_sec-0.1.2.tar.gz
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | aga_sec-0.1.2.tar.gz |
|---|---|
| Size | 133.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b89f04f81fb42bfc3b09662dfd79ff0b88567adafca1c9f86f1e7afd05bfafcc
|
|
BLAKE2b-256 checksum How to use checksums |
886631e1450f3843903bffad7a5385f40bea9f3590957ebd7d5cc47524a4dbec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Release files / aga_sec-0.1.2-py3-none-any.whl
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | aga_sec-0.1.2-py3-none-any.whl |
|---|---|
| Size | 54.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
81fa21100c021764137b69039f7d150717dba469eca88987fd06cae6bef293be
|
|
BLAKE2b-256 checksum How to use checksums |
8a386c5b47231318b9aba1ad50842080c8b0a64217ad0b1d9db7f8ce5eb09869
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Security for aga-sec 0.1.2
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.
Loss of provenance
A previous release of these files had provenance metadata, but this release does not.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Release comparison
- Removed 0.1.0 2 files With provenance
- Added 0.1.2 2 files Without provenance
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.