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 ncaq/konoka --skill githubgit clone --depth 1 https://github.com/ncaq/konokaWrote 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/ncaq/konoka/github)<a href="https://agentmods.dev/skills/ncaq/konoka/github"><img src="https://agentmods.dev/badge/skills/ncaq/konoka/github/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/ncaq/konoka/github"><img src="https://agentmods.dev/badge/skills/ncaq/konoka/github.svg" alt="Reviewed on agentmods" width="80" 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.00045 | $0.00679 |
| Opus 5.5 | $0.00018 | $0.00272 |
| Sonnet 5.5 | $0.00009 | $0.00136 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
github 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 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.
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.
What it actually says
GitHubへのアクセス方法
直接URLアクセスの問題点
GitHubのURLをWebFetchなどで直接取得することは避けてください。 以下の問題が発生します。
- プライベートリポジトリにはアクセスできない。
- HTMLページは構造化されておらずLLMには扱いにくい。
- レート制限に引っかかりやすい。
推奨されるアクセス方法
GitHub MCP
GitHub MCPが利用可能な場合は、これを優先して使用してください。
mcp__github__で始まるツールが利用可能です。
主要なツール:
mcp__github__get_file_contents: ファイル内容の取得mcp__github__issue_read: Issue情報の取得mcp__github__pull_request_read: Pull Request情報の取得- method=
get_statusでGitHub Actionsのビルド・チェック結果を確認可能
- method=
mcp__github__search_code: コード検索mcp__github__search_issues: Issue検索mcp__github__list_commits: コミット一覧の取得
GitHub CLI
MCPが使えない場合はGitHub CLI(gh)を使用してください。
推奨するコマンド例:
gh repo view owner/repo: リポジトリ情報の表示gh issue view 123 --repo owner/repo: Issue情報の表示gh pr view 456 --repo owner/repo: Pull Request情報の表示gh pr diff 456 --repo owner/repo: Pull Requestの差分表示gh release list --repo owner/repo: リリース一覧の表示
GitHub Actions関連
gh run list --repo owner/repo: ワークフロー実行一覧の表示gh run view RUN_ID --repo owner/repo: 特定の実行の詳細表示gh run view RUN_ID --repo owner/repo --log: 実行ログの表示gh run view RUN_ID --repo owner/repo --log-failed: 失敗したジョブのログのみ表示gh workflow list --repo owner/repo: ワークフロー一覧の表示
非推奨
gh apiコマンドは低レベルすぎるため非推奨です。
理由:
- 人間が承認時に何が実行されるか理解しにくい。
- 高レベルなサブコマンドで同じことができる場合が多い。
- エンドポイントの知識が必要になる。
代わりにgh issue, gh pr, gh repoなどの専用サブコマンドを使用してください。
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 · 65 lines · 45 tokens per session scan A 27fc20a26209
github is a skill published in the GitHub repository ncaq/konoka (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 45 tokens to every session and 679 once invoked, about $0.0002 per session on Opus 5.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-31.
Other skills, from other repositories
cloudflare-workers-ci-cd
Complete CI/CD guide for Cloudflare Workers using GitHub Actions and GitLab CI. Use for automated testing, deployment pipelines, preview environments, secrets management, or encountering deployment failures, workflow errors, environment configuration issues.
claude-code-bash-patterns
Claude Code Bash tool patterns with hooks, automation, git workflows. Use for PreToolUse hooks, command chaining, CLI orchestration, custom commands, or encountering bash permissions, command failures, security guards, hook configurations.
git-commit
Turn the working changes into one or more atomic commits with well-written messages. Use whenever the user runs /git-commit or asks to commit their work, wrap up a feature, or "commit what I have.".
review
Review a change with what this repository knows about it — who depends on the file, which tests cover it, what broke here before, and what the repo has written down. Use before approving a diff, opening a PR, or when asked to review.
milestone
Record a change that reshaped the repository — what moved, why it was worth doing, and which areas it touched. Use after a migration, a rewrite, or a decision that changed how part of the system works.
git-workflow
Enforces the release-branch Git model: scaffold feature branches, open PRs with review checks, cut releases with tags, and view workflow reference.