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 codemie-ai/codemie-code --skill report-issuegit clone --depth 1 https://github.com/codemie-ai/codemie-codeWrote 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/codemie-ai/codemie-code/report-issue)<a href="https://agentmods.dev/skills/codemie-ai/codemie-code/report-issue"><img src="https://agentmods.dev/badge/skills/codemie-ai/codemie-code/report-issue/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/codemie-ai/codemie-code/report-issue"><img src="https://agentmods.dev/badge/skills/codemie-ai/codemie-code/report-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 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 140 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 Privilege Escalation · line 42 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium Privilege Escalation · line 43 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium Excessive Agency · line 109 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Rogue Agent · line 243 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00187 | $0.02262 |
| Opus 5.5 | $0.00075 | $0.00905 |
| Sonnet 5.5 | $0.00037 | $0.00452 |
| Haiku 4.5 | $0.00019 | $0.00226 |
Grade B, and why
report-issue scanned grade B 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 1mo 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
> - **Linux (apt)**: `sudo apt install gh` How it starts
The opening of the file, as written. The whole thing — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Report Issue to CodeMie Code
Help the user file a well-structured bug report or feature request to codemie-ai/codemie-code on GitHub.
The goal is to create a rich issue that gives maintainers everything they need to triage and reproduce the problem — without requiring the user to manually gather technical details.
Step 1: Pre-flight and Diagnostic Collection
1a. Check gh CLI first — do this before anything else
if ! command -v gh &>/dev/null; then
echo "GH_NOT_INSTALLED"
else
gh auth status 2>&1 || echo "GH_NOT_AUTHENTICATED"
fi
If GH_NOT_INSTALLED: Stop immediately and tell the user:
"
gh(GitHub CLI) is not installed. It is required to create issues from the terminal.Install it with one of:
- macOS:
brew install gh- Linux (apt):
sudo apt install gh- Linux (dnf):
sudo dnf install gh- Windows:
winget install --id GitHub.cli- Or download from: https://cli.github.com
After installing, run
gh auth loginto connect your GitHub account, then try this skill again."
If GH_NOT_AUTHENTICATED: Stop and tell the user:
"
ghis installed but not authenticated. Rungh auth loginto connect to your GitHub account, then try again."
Do not proceed past this point until gh is installed and authenticated.
1b. Gather diagnostic context
Run the following and capture results. Don't display raw output yet.
# OS + platform
uname -srm 2>/dev/null || echo "unknown"
# Node.js version
node --version 2>/dev/null || echo "not found"
# npm version
npm --version 2>/dev/null || echo "not found"
# CodeMie CLI version
codemie --version 2>/dev/null || echo "not found"
# Installed agents and versions
codemie list --installed 2>/dev/null || echo "unavailable"
# Full doctor output (profile, provider, dependency health, agent versions)
codemie doctor 2>/dev/null || echo "unavailable"
# Shell + terminal environment
echo "Shell: $SHELL"
echo "Terminal: ${TERM_PROGRAM:-unknown}"
# Extract ERROR and WARN lines from the two most recent log files.
# Log format: [TIMESTAMP] [LEVEL] [agent] [session-id] [profile] [component] message
# Files: ~/.codemie/logs/debug-YYYY-MM-DD.log (one per day, can be several MB)
LOG_DIR="$HOME/.codemie/logs"
RECENT_LOGS=$(ls -t "$LOG_DIR"/debug-*.log 2>/dev/null | head -2)
if [ -n "$RECENT_LOGS" ]; then
echo "=== ERROR and WARN entries from recent logs ==="
# Print filename headers and filter by level; limit to last 100 matches to keep size reasonable
for f in $RECENT_LOGS; do
echo "--- $f ---"
grep -E '\[(ERROR|WARN)\]' "$f" | tail -50
done
echo "=== Full log files ==="
for f in $RECENT_LOGS; do
echo "$f"
done
else
echo "No debug logs found"
fi
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.
- 1mo ago First seen · 290 lines · 187 tokens per session scan B 721a30f83d2c
report-issue is a skill published in the GitHub repository codemie-ai/codemie-code (302 stars, last pushed today), licensed Apache-2.0. It adds 187 tokens to every session and 2,262 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…