geo-software-security-audit SKILL.md skillA
geo-software-security-audit from yuiseki/geo-software-factory is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yuiseki/geo-software-factory/geo-software-security-audit@git:20261113.0d9593dPins git:20261113.0d9593d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yuiseki/geo-software-factory
- Path
.agents/skills/geo-software-security-audit/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261113.0d9593d, committed Nov 13, 2026
- First version recorded
- Nov 12, 2026
- Size
- 12,020 bytes
- Repository stars
- 12
- License
- Apache-2.0
自分たちの地図プロダクトのセキュリティを、実装とは別の監査者が調べる。データの漏れや改ざんだけでなく、濫用と使い切り (サインアップし放題、巨大な範囲の要求、メールの送られ放題、タイルやジオコーダの従量課金の食い潰し) で壊れることまでを、認証、認可、注入、濫用、露出の 5 つの領域で当てる。誰でも使える入口を洗い出し、コードを追って候補を見つけ、手元かプレビューで再現して確かめ、「問題あり」「防御されている」「該当なし」「未確認」に分け、深刻度と対策そのものを疑い直す。確かめた問題は評価のシナリオにして退行を防ぐ。「セキュリティが心配」「脆弱性を調べて」「公開して大丈夫か」「濫用されないか」「レートリミットは要るか」と言われたとき、geo-software-build のあと geo-software-deploy の前と、公開のあとの定期の点検で使う。.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# geo-software-security-audit ダークファクトリーでは、人間がコードをレビューしない。だから、セキュリティも人間の目ではなく、実装と切り離した監査で確かめる。監査は、何が守られていれば良いかを人間が昼に決め、夜に実装者と別の監査者が、誰でも使える入口から攻め手の目で調べる。 サービスは、個人情報が漏れなくても、データが改ざんされなくても壊れる。登録し放題から決済を試され放題になる、数千文字の要求一つで裏の検索や DB が止まる、パスワードの再設定のメールが何万通も送られて送信元がスパム扱いになる。地図のプロダクトでは、これに、全世界を囲む範囲の要求、頂点が百万ある図形、地図の読み込みごとに課金されるタイルの鍵の流用、利用者の正確な位置の推定が加わる。教科書にもバグバウンティにも出にくいこれらを、漏れや改ざんと同じ重さで調べる。 | reference | 読むとき | 中身 | |---|---|---| | [entrypoints](references/entrypoints.md) | 最初に | 認証なしの入口と、誰でもすぐ作れる一般の利用者の入口の洗い出し。地図のプロダクトに特有の入口 | | [auth](references/auth.md) | 認証と認可を調べるとき | 登録とログインの迂回、トークンの検証、取り消し後の残り、他人のデータ (IDOR)、権限の出どころ、画面で隠すだけの制御、タイルに漏れる非公開の属性 | | [injection](references/injection.md) | 外からの入力の流れを調べるとき | 地物の属性からポップアップへの HTML、スタイルやタイルの URL、空間の SQL、検索語、取り込むファイル (KML、GPX、Shapefile の ZIP)、書き出す CSV | | [abuse](references/abuse.md) | 濫用と使い切りを調べるとき | 登録と決済、巨大な要求、メールと SMS、従量課金の上流、応答の違いからの推測。対策が新しい DoS にならないか | | [exposure](references/exposure.md) | 公開されるものを調べるとき | 公開の面、ヘッダ、配布物の中の秘密、プレビューの URL、利用者の位置の露出、依存と CI | | [gov-enterprise-audit](references/gov-enterprise-audit.md) | 自治体・業務システムを監査するとき | 三層分離と無害化境界、操作監査ログ (Audit Trail)、ISMAP・閉域 TLS 観点 | …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_urhgdce32owzvhpe/4176e45d311ac35dc017759bb982b9696982270f449edcdc2c7168f4e7577559.json
Then /plugin install geo-software-security-audit@markdownregistry-urhgdce32owzvhpe in Claude Code. It installs git:20261113.0d9593d, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add yuiseki/geo-software-factory/geo-software-security-audit@sha256:4176e45d311ac35dThe line at the top of this page pins the label git:20261113.0d9593d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_urhgdce32owzvhpe)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in yuiseki/geo-software-factory/geo-software-security-audit since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of geo-software-security-audit from somewhere else? Ask it: where did my geo-software-security-audit come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 3 versions of this file, between Nov 12, 2026 and Nov 13, 2026, more than one a day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261113.0d9593d latest | 2026-11-13 | 0d9593d | 12,020 B | A | view · diff |
| git:20261113.a912aab | 2026-11-13 | a912aab | 11,807 B | A | view · diff |
| git:20261112.edc397f | 2026-11-12 | edc397f | 11,450 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/geo-software-security-audit/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (12020 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
yuiseki/geo-software-factory · 12 stars · license Apache-2.0 · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_urhgdce32owzvhpe GET https://markdownregistry.com/api/v1/resolve?ref=yuiseki/geo-software-factory/geo-software-security-audit GET https://markdownregistry.com/api/v1/blob/4176e45d311ac35dc017759bb982b9696982270f449edcdc2c7168f4e7577559
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from yuiseki/geo-software-factory
Every file in yuiseki/geo-software-factory
Browse by kind, by grade A, or by owner.
Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.