Our take
Quietno commits in the last 90 days- Activity
- 42
- Community
- 4
- Issues
- 21
- Pull requests
- 21
- Fewer contributors than 92% of the projects we track
Agent Feed offers a concrete, repository-centered way to govern AI coding, but its quiet recent activity and reliance on one contributor make ongoing maintenance worth checking before adoption.
Good fit if
- You use Codex, Claude Code, or Cursor and want a common source of workflow guidance in the repository.
- Your team values explicit scope, verification, review, and human decision gates for AI-generated changes.
- You can run a Python 3.11+ CLI and are comfortable adopting an MIT-licensed project whose work is concentrated in one contributor.
Look elsewhere if
- You need a hosted service or runtime platform rather than repository-installed workflow files and checks.
- You need evidence of ongoing commits or issue and pull-request handling: the project is marked quiet, with no commits or closed issues or merged pull requests in the measured recent period.
- Your workflow does not use the supported coding-agent adapters and a shared AGENTS.md protocol would add little value.
All health signals
| Last commit | 2026-05-09 (5 months ago) |
|---|---|
| Commits, last 90 days | 0 |
| Releases, last 12 months | 9 (latest v1.1.6, 2026-05-08) |
| Contributors | 1 |
| Issues closed, last 90 days | 0 |
| Pull requests merged, last 90 days | 0 |
| Project age | 5 months |
Checked on 2026-10-12 with the GitHub API.
Overview
Agent Feed is a Python CLI that installs workflow instructions and supporting checks into a code repository. It addresses the fragmentation that occurs when AI coding guidance lives across chat history, tool-specific rules, and scattered project documents.
The installed protocol uses AGENTS.md as a shared entry point, with rules, skills, project knowledge, verification steps, and adapters for Codex, Claude Code, and Cursor. It is designed for teams that want AI-assisted changes to follow repository-defined scope, decision, review, and handoff practices.
Key Features
- Initializes a repository with
AGENTS.mdand a structured.agents/workflow. - Provides thin adapters for Codex, Claude Code, and Cursor, keeping the shared protocol canonical.
- Defines task boundaries, decision checkpoints, verification gates, review, and session handoff.
- Checks protocol structure, references, scripts, skills, and client adapters.
- Supports project-specific constraints and domain knowledge alongside reusable workflow rules.
- Manages local and imported skills, with trust checks for external assets.
- Includes status, upgrade, adapter sync, and configuration commands in its CLI.
Use Cases
- A team using several AI coding tools wants repository instructions to stay consistent across clients.
- Developers want small coding requests to remain scoped and architecture or contract decisions to receive human confirmation.
- Teams need completion to include project-defined tests, documentation checks, or review rather than relying on chat claims.
- A developer working across long AI sessions wants a concise handoff of active conclusions instead of replaying conversation history.
- Maintainers want to add team-specific skills and constraints without replacing a shared workflow foundation.
What you need
Detected in the repository
- Node.js >=16.0.0 (from package.json)
- Python >=3.11 (from pyproject.toml)
- A test suite and automated checks on GitHub Actions
License in plain words
MITpermissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the copyright and license notice
- Share your changes: no
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
Install with one of the supported package managers, then initialize and check the repository:
uv tool install agent-feed
agent-feed init
agent-feed check
See the README and Usage Guide for setup options and customization.
Alternatives
- compound-engineering-plugin: It packages reusable skills for planning through implementation and captured learnings, rather than installing a repository-owned workflow with shared checks and gates.
- agent-skills: It offers portable engineering workflows for planning, testing, review, and release, while agent-feed centers on a repository-owned setup with tool adapters.
- agent-skills: It provides reusable specification, review, testing, and sprint skills, rather than a repository-owned workflow with shared instructions and checks.
- agentic-engineering: It emphasizes documentation, session memory, and human-controlled merges, while agent-feed installs shared workflow gates and tool adapters in a repository.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| agent-feed | Python | MIT | 4 | Quiet |
| compound-engineering-plugin | TypeScript | MIT | 25.4k | Active |
| agent-skills | JavaScript | MIT | 101k | Active |
| agent-skills | Shell | MIT | 2 | Active |
| agentic-engineering | – | MIT | 5 | Quiet |
Considerations
- The measured project status is quiet: there have been no commits in the recent measured period, despite releases during the past year. Release activity does not by itself establish current maintenance.
- The project has one contributor, with nearly all contribution activity concentrated there. This creates a maintainer-continuity risk for a workflow teams may depend on.
- The CLI requires Python 3.11 or newer. The npm package is a wrapper and also requires Python on the machine.
- Agent Feed installs and validates instructions and workflow assets; it is not a replacement for the coding agents themselves or for project-specific test infrastructure.
Found this useful?
Share it with someone who would like agent-feed.