Copilot Linker
A cross-platform Python utility to link agents and skills from the awesome-copilot repository to any local git repository.
Installation
Install from source:
pip install .
Or for development:
pip install -e .
From PyPI (once published):
pip install gh-agent-sync
Usage
Run the utility from the root of your git repository:
Link Agents and Skills
gh-agent-sync link
Or specify a custom repository:
gh-agent-sync link --url https://github.com/your-org/your-agents-repo
This will:
- Clone or update the awesome-copilot repository into
.github/awesome-copilot - Create symbolic links (or copies if symlinks fail) to
.github/agentsand.github/skills - Add the linked paths to
.gitignoreto prevent them from being committed
Undo Linking
gh-agent-sync undo
This will:
- Remove the
.github/agentsand.github/skillsdirectories - Remove the cloned
.github/awesome-copilotrepository
Development
Building
To build the package:
python -m build
Publishing
- Create a release on GitHub
- The CI/CD workflow will automatically build and publish to PyPI
Make sure to set up PyPI API tokens in the repository secrets if needed.
What it does
- Checks if the current directory is a git repository
- Clones or updates the awesome-copilot repository into
.github/awesome-copilot - Creates symbolic links (or copies if symlinks fail):
.github/agents→.github/awesome-copilot/agents.github/skills→.github/awesome-copilot/skills
- Adds linked paths to
.gitignore
This allows you to use the agents and skills from awesome-copilot in your repository without copying the files directly.
Requirements
- Python 3.8+
- Git
- Internet connection for cloning the repository
Notes
- On systems where symlinks are not supported or require special permissions, the utility will fall back to copying the directories.
- The utility creates links/copies, so changes in the awesome-copilot repo will be reflected in your links (after updating with
git pullin the cloned directory).
Architecture
Contributing
We use a pull request workflow with automated versioning and release management. Please see CONTRIBUTING.md for detailed guidelines on:
- How to create pull requests
- Conventional commit message style
- Automated versioning and release process
All commits should follow the Conventional Commits specification.
Metadata
Release files for gh-agent-sync 1.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| gh_agent_sync-1.2.1.tar.gz | 4.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gh_agent_sync-1.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.5 kB
Release files / gh_agent_sync-1.2.1.tar.gz
| Download URL | gh_agent_sync-1.2.1.tar.gz |
|---|---|
| Size | 4.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c79133fbd3cf460680388d01a1b6180e2e985164b3a1ccbea52a18a856791d37
|
|
BLAKE2b-256 checksum How to use checksums |
045b12939cd8ea36dcba24bd1d5ed9deb95ca6b163602d4276e789f4a9bf3330
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / gh_agent_sync-1.2.1-py3-none-any.whl
| Download URL | gh_agent_sync-1.2.1-py3-none-any.whl |
|---|---|
| Size | 5.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c37ca83076215c102452786e13d97a14f29eb22debf95860aa3cb2ab6e17ef0d
|
|
BLAKE2b-256 checksum How to use checksums |
4ad8c9aceee0def317c09f24b8748488c764014161d521e5ebf01eea5fd64da2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for gh-agent-sync 1.2.1
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.