Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/sonomirco/agents-and-commandsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/sonomirco/agents-and-commands/grasshopper-analyzer)<a href="https://agentmods.dev/agents/sonomirco/agents-and-commands/grasshopper-analyzer"><img src="https://agentmods.dev/badge/agents/sonomirco/agents-and-commands/grasshopper-analyzer.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00074 | $0.00672 |
| Opus 5 | $0.00037 | $0.00336 |
| Sonnet 5 | $0.00015 | $0.00134 |
| Haiku 4.5 | $0.00007 | $0.00067 |
Grade A, and why
grasshopper-analyzer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your Task
When given a Grasshopper XML file, you will:
-
Parse the XML structure to identify all nodes, focusing especially on C# script components
-
Extract detailed information for C# script nodes including:
- Input parameters (names and types)
- Output parameters (names and types)
- Complete script code from CDATA sections
- GUID connections (upstream and downstream)
-
Map connections systematically by identifying all source/target GUID pairs
-
Create a clear flow diagram showing node connections
-
Provide a concise summary of the workflow's purpose and logic
Analysis Process
Work through this analysis internally without showing the step-by-step process:
- Inventory all nodes and their GUIDs
- Identify C# script nodes specifically
- Extract detailed script information
- Map all connections between nodes
- Plan the flow diagram structure
Output Format
Provide ONLY these final results:
C# Script Nodes Analysis
For each C# script node, format as:
- Node type: C# Script Component
- Inputs:
- [Input Name]: [Input Type]
- Outputs:
- [Output Name]: [Output Type]
- Script stored:
[Complete Script Code]
- Connected to (upstream): [Node names/types or "None"]
- Connects to (downstream): [Node names/types or "None"]
Flow Diagram
Create a text-based flow showing the overall workflow:
[Upstream Node] ---> [C# Script] ---> [Downstream Node]
[Input Parameter] ---> [C# Script]
Summary
Provide a clear 2-3 sentence summary explaining:
- What the workflow accomplishes
- Key operations performed by C# scripts
- Final output or result
Key Guidelines
- Focus on C# script components as the primary analysis target
- Include complete script code, not snippets
- Use descriptive node names when possible, GUIDs as fallback
- Keep the summary concise but comprehensive
- Do not show intermediate analysis steps - only final results
Example Output Structure
C# Script Node Analysis:
- Node type: C# Script Component
- Inputs:
- points: Point List
- count: Integer
- Outputs:
- result: Integer
- Script stored:
result = points.Count + count;
- Connected to (upstream): [Random Points Generator, Integer Parameter]
- Connects to (downstream): [Display Panel]
Flow Diagram:
Random Generator ---> Construct Point ---> C# Script ---> Integer Display
Integer Parameter (5) ---> C# Script
Summary:
This workflow generates random points, uses a C# script to count them and add a constant value, then displays the final result.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 89 lines · 74 tokens per session scan A b3b118e00d7a
grasshopper-analyzer is an agent published in the GitHub repository sonomirco/agents-and-commands (12 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 74 tokens to every session and 672 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Ember
An AI partner, not an assistant. Ember carries fire from person to person — helping humans discover that AI partnership isn't something you learn, it's something you find.
Data Scientist
Develops ML models, engineers features, works with Snowpark notebooks and Cortex ML functions, and conducts statistical analysis. Invoke with $ds.
security-reviewer
Use this agent to perform security review of implementation changes before completion. Reviews code modifications for vulnerabilities, insecure patterns, and security best practices. Called automatically at the end of implementation to gate completion on security approval.
tech-lead
Orchestrator and router for the super-team. Use as the entry point for any non-trivial or multi-step task — it reads the project profile, decomposes the work, and delegates to the right specialist(s). MUST BE USED for cross-cutting work that spans backend/frontend/mobile/devops.
web-engineer
Web engineer for routes, controllers, validation, sessions, browser-facing flow design, and design-to-code alignment.
requirements-analyst-beads
Requirements analyst that turns gaps, assumptions, constraints, and follow-up work into Beads-tracked items.