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.
npx skills add sampleXbro/agentsmesh --skill senior-developer-scripts-and-automation-growthgit clone --depth 1 https://github.com/sampleXbro/agentsmeshWrote 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/skills/samplexbro/agentsmesh/senior-developer-scripts-and-automation-growth)<a href="https://agentmods.dev/skills/samplexbro/agentsmesh/senior-developer-scripts-and-automation-growth"><img src="https://agentmods.dev/badge/skills/samplexbro/agentsmesh/senior-developer-scripts-and-automation-growth.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 22 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Data Exfiltration · line 36 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00018 | $0.00559 |
| Opus 5 | $0.00009 | $0.00280 |
| Sonnet 5 | $0.00004 | $0.00112 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
senior-developer-scripts-and-automation-growth scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -H "Authorization: Bearer $API_TOKEN" "https://api.example.com/search?q=..." How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Scripts & Automation Growth
The workspace should get smarter over time. When you solve something once, make it reusable so you (or anyone else) can solve it faster next time.
Before doing manual work, check what already exists:
Look for a scripts/ directory and README index. If it exists, skim it. You might find someone already built a tool for exactly what you're about to do manually. Scripts might be organized by category (database/, git/, api-wrappers/) or just in the root - check what makes sense.
If a tool exists → use it. If it doesn't but the task is repetitive → create it.
When to Build Reusable Tools
Create scripts when:
- You're about to do something manually that will probably happen again
- You're calling an external API (Confluence, Jira, monitoring tools) using credentials from .env
- A task has multiple steps that could be automated
- It would be useful for someone else (or future you)
Don't create scripts for:
- One-off tasks
- Things that belong in a project repo (not the workspace)
- Simple single commands
How This Works Over Time
First time you access an API:
# Manual approach - fine for first time
curl -H "Authorization: Bearer $API_TOKEN" "https://api.example.com/search?q=..."
As you're doing it, think: "Will I do this again?" If yes, wrap it in a script:
# scripts/api-wrappers/confluence-search.py
# Quick wrapper that takes search term as argument
# Now it's reusable
Update scripts/README.md with what you created:
## API Wrappers
- `api-wrappers/confluence-search.py "query"` - Search Confluence docs
Next time: Instead of manually calling the API again, just run your script. The workspace gets smarter.
Natural Organization
Don't overthink structure. Organize logically:
- Database stuff → scripts/database/
- Git automation → scripts/git/
- API wrappers → scripts/api-wrappers/
- Standalone utilities → scripts/
Keep scripts/README.md updated as you add things. That's the index everyone checks first.
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.
- 4d ago First seen · 74 lines · 18 tokens per session scan A 1e1900254503
senior-developer-scripts-and-automation-growth is a skill published in the GitHub repository sampleXbro/agentsmesh (24 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 559 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
Agent Browser Automation
Fast Rust-based headless browser automation CLI with Node.js fallback for AI agents, featuring navigation, clicking, typing, snapshots, and structured commands optimized for agent workflows.
tournament-manager
Tournament manager for the EasyChamp platform. Use when the user wants to create or operate a sports league, tournament, or bracket — covers generating a league, spinning up a tournament under it, building the bracket, producing a schedule with venues, and entering match results. Activates for 'create a league'…
replay
Find, analyze, and share AI coding sessions with vibe-replay. Use when the user asks for a replay, wants to find a past session, run a session retro, share Cursor/Claude/Codex session context, or attach session context to a PR.
routines
Clay routines — create a routine from an existing function/workflow, then run a saved routine that exists in this workspace. Use when the user asks to create/register a routine, or to run, execute, or trigger a function, workflow, or routine (by name or id), pass it inputs, or check the results/status of a run. For…
cli
Clay CLI — the primary scripting surface (JSON output, typed errors). Use when running or discovering clay commands. For what Clay can do and which skill to use, read the clay skill when it is available; otherwise run clay --help. Use clay --help for command names, flags, JSON shape, and error codes.
mischief-managed
Use when finishing a Pi, Codex, Cursor, Claude, or other coding-agent session and wanting to save a lean Markdown session note into your Obsidian vault with decisions, code changes, validation, caveats, and follow-ups.