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 CodeInfinity1/Stram --skill github-issuesgit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/github-issues)<a href="https://agentmods.dev/skills/codeinfinity1/stram/github-issues"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/github-issues.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.00034 | $0.00542 |
| Opus 5 | $0.00017 | $0.00271 |
| Sonnet 5 | $0.00007 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
github-issues 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 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.
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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issues
Purpose
Manage issue workflows without losing context. This skill helps turn bugs, feature requests, logs, and investigations into clear GitHub issue records.
When To Use
Use for issue creation, triage, updates, linking PRs, labeling, milestones, and summarizing issue state.
Inputs And Evidence
- Repo, issue number/title, labels, severity, reproduction, logs, screenshots, and desired action.
- gh auth status or API setup.
Tool Map
github_issue_packet_creategithub_artifact_inspectsecret_scan_report_createapproval_policy_review_createrun_shell_commandread_filewrite_notesystematic-debuggingstatus-update-writing
Workflow
- Identify repo and issue intent.
- Gather reproduction or evidence before drafting.
- Use
github_issue_packet_createto create a local issue packet with title, problem, expected behavior, actual behavior, steps, impact, labels, and evidence. - Inspect the packet with
github_artifact_inspectbefore posting, sharing, or referencing it as a final artifact. - Use
secret_scan_report_createor an equivalent review before including logs, configs, screenshots, or customer data. - Use
gh issueonly when configured and the user wants live GitHub action. - For updates, inspect current issue state first.
- Report exact created/updated URL or keep as a draft.
Native Implementation Boundaries
- Use native Stram GitHub packet tools first for drafts and triage.
- Use native shell/gh only for approved live GitHub action.
- Do not import external reference GitHub issue scripts.
- Do not pretend GitHub was updated when only a draft was written.
Safety And Approval
- Public or team-visible issue creation/update needs user approval.
- Redact secrets, customer data, tokens, and private logs.
- Confirm repo before posting.
Verification
- Live updates require a URL or command output.
- Drafts should be clearly marked unsent with
live_execution_status: not_executed. - Labels/milestones should match existing repo choices when checked.
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 · 73 lines · 34 tokens per session scan A a13fb7256d44
github-issues is a skill published in the GitHub repository CodeInfinity1/Stram (10 stars, last pushed 28d ago), licensed MIT. It adds 34 tokens to every session and 542 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
postmortem
Deliver a structured post-mortem after incidents, mistakes, or stuck sessions. Use when the user requests a structured post-mortem after incidents, mistakes, or stuck sessions.
incident-postmortem
Build a blameless incident report and release follow-up tasks.
linear-update
Update Linear issues with debugging findings. Add comments, change status, update labels, set priority. Use after completing investigations.
report-issue-local
File a bug or feature request against this MCP server's own repo. Use for server-specific issues — tool logic, service integrations, config problems, or domain bugs that aren't caused by the framework.
postmortem-writing
Write effective blameless postmortems with root cause analysis, timelines, and action items. Use when conducting incident reviews, writing postmortem documents, or improving incident response processes.
omh-agent-board
This is a Hermes-native agent-board workflow skill.