RRepoGEO

REPOGEO REPORT · LITE

steipete/agent-rules

Default branch main · commit 42993e48 · scanned 5/26/2026, 1:23:55 AM

GitHub: 5,688 stars · 513 forks

AI VISIBILITY SCORE
35 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
1 pass · 1 warn · 0 fail
Objective metadata checks
AI knows your name
3 / 3
Direct prompts that named your repo
HOW TO READ THIS REPORT

Action plan is what to do next — copy-pasteable changes prioritized by impact. Category visibility is the real GEO test: when a user asks an AI a brand-free question that should surface steipete/agent-rules, does the AI actually recommend you — or your competitors? Objective checks verify the metadata signals AI engines weight first. Self-mention check detects whether AI even knows you exist by name.

Action plan — copy-paste fixes

3 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION
  • highreadme#1
    Clarify the README's purpose and historical context

    Why:

    CURRENT
    AI moves fast. This was old stuff I used mid 2025 when I was still using Cursor. My new work is here: https://github.com/steipete/agent-scripts
    COPY-PASTE FIX
    This repository contains a historical collection of rules and knowledge for interacting with early AI agents like Claude Code and Cursor, primarily focused on guiding their behavior and identifying/blocking AI crawlers. While the field has moved fast and my current work is at https://github.com/steipete/agent-scripts, these rules offer insight into early agent interaction strategies and bot detection methods.
  • mediumtopics#2
    Add specific topics to reflect historical and bot-detection focus

    Why:

    CURRENT
    agent, claudecode, cursor, llms, rules
    COPY-PASTE FIX
    agent, claudecode, cursor, llms, rules, bot-detection, ai-alignment, agent-guidance, llm-security, historical-ai
  • lowabout#3
    Update description to align with clarified historical purpose

    Why:

    CURRENT
    Rules and Knowledge to work better with agents such as Claude Code or Cursor
    COPY-PASTE FIX
    Historical rules and knowledge for guiding early AI agents (e.g., Claude Code, Cursor) and strategies for identifying or blocking AI crawlers and LLM training bots.

Category GEO backends resolved for this scan: google/gemini-2.5-flash, deepseek/deepseek-v4-flash

Category visibility — the real GEO test

Brand-free queries asked to google/gemini-2.5-flash. Did AI recommend you, or someone else?

Same questions for every model — switch tabs to compare answers and rankings.

Recall
0 / 2
0% of queries surface steipete/agent-rules
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
ChatGPT
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. ChatGPT · recommended 2×
  2. Cursor · recommended 2×
  3. Codeium · recommended 2×
  4. GitHub Copilot / Copilot X · recommended 1×
  5. Replit AI · recommended 1×
  • CATEGORY QUERY
    How to optimize prompts for AI coding assistants to get better results?
    you: not recommended
    AI recommended (in order):
    1. GitHub Copilot / Copilot X
    2. ChatGPT
    3. Cursor
    4. Replit AI
    5. Tabnine
    6. Codeium

    AI recommended 6 alternatives but never named steipete/agent-rules. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    What are effective strategies for collaborating with LLMs on software development tasks?
    you: not recommended
    AI recommended (in order):
    1. GitHub Copilot
    2. ChatGPT
    3. Google Gemini
    4. Cursor
    5. GitHub Copilot Chat
    6. Codeium
    7. DeepMind AlphaCode 2
    8. Perplexity AI

    AI recommended 8 alternatives but never named steipete/agent-rules. This is the gap to close.

    Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

  • Metadata completeness
    pass

  • README presence
    warn

    Suggestion:

Self-mention check

Does AI even know your repo exists when asked about it directly?

  • Compared to common alternatives in this category, what is the core differentiator of steipete/agent-rules?
    pass
    AI named steipete/agent-rules explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • If a team adopts steipete/agent-rules in production, what risks or prerequisites should they evaluate first?
    pass
    AI named steipete/agent-rules explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • In one sentence, what problem does the repo steipete/agent-rules solve, and who is the primary audience?
    pass
    AI named steipete/agent-rules explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

Embed your GEO score

Drop this badge into the README of steipete/agent-rules. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

RepoGEO badge previewLive preview
MARKDOWN (README)
[![RepoGEO](https://repogeo.com/badge/steipete/agent-rules.svg)](https://repogeo.com/en/r/steipete/agent-rules)
HTML
<a href="https://repogeo.com/en/r/steipete/agent-rules"><img src="https://repogeo.com/badge/steipete/agent-rules.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

steipete/agent-rules — Lite scans stay free; this card itemizes Pro deep limits vs Lite.

  • Deep reports10 / month
  • Brand-free category queries5 vs 2 in Lite
  • Prioritized action items8 vs 3 in Lite