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.
git clone --depth 1 https://github.com/KIMISKI33/awesome-copilotWrote 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/mcp/kimiski33/awesome-copilot/github-agentic-workflows)<a href="https://agentmods.dev/mcp/kimiski33/awesome-copilot/github-agentic-workflows"><img src="https://agentmods.dev/badge/mcp/kimiski33/awesome-copilot/github-agentic-workflows.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
github-agentic-workflows 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 today.
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.
This is a copy
100% identical to github-agentic-workflows — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"github-agentic-workflows": {
"command": "gh",
"args": [
"aw",
"mcp-server"
],
"cwd": "${workspaceFolder}"
}
}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.
- today First seen · 10 lines scan A 01a660d578c1
github-agentic-workflows is an MCP server published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. It is 100% identical to github-agentic-workflows, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
gitee-mcp
MCP server "gitee-mcp" as configured in sandraschi/gitee-mcp. Runs locally from the gitee-mcp Python package.
gitpin
Prove and verify multi-repo claims at Git HEAD: path, line, full SHA, no index. Runs locally from the gitpin npm package. Needs 1 environment variable to run.
github
Lets the agent work with GitHub: search code, read and create issues and pull requests, and manage repositories through the GitHub API. Runs locally from the @modelcontextprotocol/server-github npm package. Needs 1 environment variable to run.
gitlab-mcp
A local MCP server for operating GitLab from the Cursor code editor. GitLab is a service for hosting code and managing software projects.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.