Skip to the content.

Community Contributions

Guardian agent prompt patterns have been contributed to repositories across the AI ecosystem. Each contribution is tailored to the target repository’s format and adds genuine value – full applications, detailed prompts, workflow templates, and quality gate agents.

Contribution Map

Repository Stars PR Type Status
awesome-llm-apps 104K #692 Streamlit multi-agent app Open
everything-claude-code 141K #1299 Agent definition (YAML) Open
system-prompts-and-models 134K #422 System prompt + README Open
claude-code-best-practice 32K #43 6 production patterns Open
awesome-ai-agents 27K #693 Directory listing Open
awesome-n8n-templates 20K #99 n8n workflow JSON Open
awesome-claude-code-subagents 16K #180 Quality gate agent Open
claude-code-system-prompts 8.3K #16 Orchestrator example Open
awesome-ai-system-prompts 5.6K #41 Prompt collection listing Open
claude-code-ultimate-guide 2.9K #21 Agent example Open
a-list-of-claude-code-agents 1.2K #16 Multi-agent orchestrator Open
awesome-claude-code-toolkit 1.1K #217 Quality gate agent Open
antigravity-awesome-skills 31K #462 Multi-agent orchestrator skill Open
leaked-system-prompts 14K #149 Open-source orchestrator prompt Open

Combined audience: 538K+ stars across 14 repositories.

What We Contribute

Full Applications

For repos like awesome-llm-apps, we built a complete Streamlit multi-agent task orchestrator with 5 specialized agents, SQLite anti-duplication, quality gates, and multi-provider support (OpenAI, Anthropic, demo mode).

Production Prompts

For prompt collections like system-prompts-and-models, we contributed the actual production orchestrator prompt alongside system prompts from Cursor, Devin, and Codex CLI.

Agent Definitions

For agent repos like everything-claude-code, we added a multi-agent orchestrator in the exact YAML frontmatter format the repo uses.

Workflow Templates

For automation repos like awesome-n8n-templates, we contributed a real n8n workflow JSON with 13 nodes for AI agent orchestration.

Patterns That Make PRs Merge

Based on our experience submitting 12 PRs:

  1. Match the format exactly. If a repo uses tables, submit a table entry. If it uses YAML frontmatter, match the schema.
  2. Add real value. A link is low-effort. A working app, detailed prompt, or importable workflow is high-effort and high-merge-probability.
  3. Respond to automated reviews. Bots like CodeRabbit and Greptile flag issues within minutes. Fixing them fast signals quality.
  4. Keep scope tight. One file or one section per PR. Don’t restructure someone else’s repo.
  5. Write good PR descriptions. Explain what the contribution adds and why the repo’s audience would find it useful.

Try These Patterns Yourself

The orchestration patterns behind all these contributions come from Guardian’s production system:


Back to Guardian Agent Prompts Docs Home