[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79N6JDG032BDAM6VZ20QMH3":3,"skill-same:01M79N6JDG032BDAM6VZ20QMH3":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M79N6JDG032BDAM6VZ20QMH3","cisco-ios-patterns",null,"Cisco IOS and IOS-XE review patterns for show commands, config hierarchy, wildcard masks, ACL placement, interface hygiene, and safe change-window verification. Use when reading, writing, or reviewing Cisco IOS \u002F IOS-XE configuration or planning a change window.","JunMystery\u002FAgent-Guidance","JunMystery","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F161468934?v=4","01M79MTMV8F0BY8NK1A92RA8A0","Jun","01M79MTMWCFBKPHN5B25E6V20B",0,"MIT","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fcisco-ios-patterns\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cisco-ios-patterns\ndescription: Cisco IOS and IOS-XE review patterns for show commands, config hierarchy, wildcard masks, ACL placement, interface hygiene, and safe change-window verification. Use when reading, writing, or reviewing Cisco IOS \u002F IOS-XE configuration or planning a change window.\nmetadata:\n  origin: community\n---\n\n# Cisco IOS Patterns\n\nUse this skill when reviewing Cisco IOS or IOS-XE snippets, building a\nchange-window checklist, or explaining how to collect evidence from a router or\nswitch without making the incident worse.\n\n## When to Use\n\n- Reviewing IOS or IOS-XE configuration before a planned change.\n- Choosing read-only `show` commands for troubleshooting.\n- Checking ACL wildcard masks and interface direction.\n- Explaining global, interface, routing process, and line configuration modes.\n- Verifying that a change landed in running config and was saved intentionally.\n\n## Operating Rules\n\nTreat IOS examples as patterns, not paste-ready production changes. Confirm the\nplatform, interface names, current config, rollback path, and out-of-band access\nbefore making changes on a real device.\n\nPrefer this workflow:\n\n1. Capture current state with read-only commands.\n2. Review the exact candidate config.\n3. Confirm management access cannot be locked out.\n4. Apply the smallest change in a maintenance window.\n5. Re-read state, compare to the baseline, then save only after validation.\n\n## Mode Reference\n\n```text\nRouter> enable\nRouter# show running-config\nRouter# configure terminal\nRouter(config)# interface GigabitEthernet0\u002F1\nRouter(config-if)# description UPLINK-TO-CORE\nRouter(config-if)# no shutdown\nRouter(config-if)# exit\nRouter(config)# end\nRouter# show running-config interface GigabitEthernet0\u002F1\n```\n\n`running-config` is active memory. `startup-config` is what survives reload.\nDo not save a change just because a command was accepted; validate behavior\nfirst, then use `copy running-config startup-config` if the change is approved.\n\n## Read-Only Collection\n\n```text\nshow version\nshow inventory\nshow processes cpu sorted\nshow memory statistics\nshow logging\nshow running-config | section line vty\nshow running-config | section interface\nshow running-config | section router bgp\nshow ip interface brief\nshow interfaces\nshow interfaces status\nshow vlan brief\nshow mac address-table\nshow spanning-tree\nshow ip route\nshow ip protocols\nshow ip access-lists\nshow route-map\nshow ip prefix-list\n```\n\nCollect the specific section you need instead of dumping full config into a\nticket when the config may contain secrets, customer names, or private topology.\n\n## Wildcard Masks\n\nIOS ACL and many routing statements use wildcard masks, not subnet masks.\n\n```text\nSubnet mask       Wildcard mask\n255.255.255.255   0.0.0.0\n255.255.255.252   0.0.0.3\n255.255.255.0     0.0.0.255\n255.255.0.0       0.0.255.255\n```\n\nReview wildcard masks before deployment. A subnet mask accidentally used as a\nwildcard can match far more traffic than intended.\n\n```text\nip access-list extended WEB-IN\n  10 permit tcp 192.0.2.0 0.0.0.255 any eq 443\n  999 deny ip any any log\n```\n\nEvery ACL has an implicit deny at the end. Add an explicit logged deny when the\noperational goal includes observing misses, and confirm logging volume is safe.\n\n## ACL Placement Review\n\nBefore applying an ACL to an interface, answer these questions:\n\n- Which traffic direction is being filtered, `in` or `out`?\n- Is management traffic sourced from a known jump host or management subnet?\n- Is there an explicit permit for required routing, DNS, NTP, monitoring, or\n  application traffic?\n- Are hit counters available from a safe test source?\n- Is there a rollback command and an active console or out-of-band path?\n\nDo not test reachability by removing firewall or ACL protections. Read counters,\nlogs, and route state first.\n\n## Interface Hygiene\n\n```text\ninterface GigabitEthernet0\u002F1\n description UPLINK-TO-CORE\n switchport mode trunk\n switchport trunk allowed vlan 10,20,30\n switchport trunk native vlan 999\n no shutdown\n```\n\nUse clear descriptions, explicit switchport mode, and documented native VLANs.\nOn routed interfaces, confirm the mask, peer addressing, and routing process\nbefore assuming link state means forwarding is correct.\n\n## Change-Window Verification\n\nUse before\u002Fafter checks that match the actual change.\n\n```text\nshow running-config | section interface GigabitEthernet0\u002F1\nshow interfaces GigabitEthernet0\u002F1\nshow logging | include GigabitEthernet0\u002F1|changed state|line protocol\nshow ip route \u003Cprefix>\nshow ip access-lists \u003Cname>\n```\n\nFor routing changes, also capture neighbor state and route tables before and\nafter the change. For ACL changes, compare hit counters from a planned test\nsource rather than relying on a generic ping.\n\n## Anti-Patterns\n\n- Applying a generated config without a device-specific diff.\n- Saving configuration before post-change checks pass.\n- Using a subnet mask where IOS expects a wildcard mask.\n- Applying an ACL to the wrong interface direction.\n- Troubleshooting by disabling ACLs, route policies, or authentication.\n- Pasting full configs into public tools without sanitizing secrets and topology.\n\n## See Also\n\n- Agent: `network-config-reviewer`\n- Agent: `network-troubleshooter`\n- Skill: `network-config-validation`\n- Skill: `network-interface-health`\n","# Cisco IOS Patterns\n\nUse this skill when reviewing Cisco IOS or IOS-XE snippets, building a\nchange-window checklist, or explaining how to collect evidence from a router or\nswitch without making the incident worse.\n\n## When to Use\n\n- Reviewing IOS or IOS-XE configuration before a planned change.\n- Choosing read-only `show` commands for troubleshooting.\n- Checking ACL wildcard masks and interface direction.\n- Explaining global, interface, routing process, and line configuration modes.\n- Verifying that a change landed in running config and was saved intentionally.\n\n## Operating Rules\n\nTreat IOS examples as patterns, not paste-ready production changes. Confirm the\nplatform, interface names, current config, rollback path, and out-of-band access\nbefore making changes on a real device.\n\nPrefer this workflow:\n\n1. Capture current state with read-only commands.\n2. Review the exact candidate config.\n3. Confirm management access cannot be locked out.\n4. Apply the smallest change in a maintenance window.\n5. Re-read state, compare to the baseline, then save only after validation.\n\n## Mode Reference\n\n```text\nRouter> enable\nRouter# show running-config\nRouter# configure terminal\nRouter(config)# interface GigabitEthernet0\u002F1\nRouter(config-if)# description UPLINK-TO-CORE\nRouter(config-if)# no shutdown\nRouter(config-if)# exit\nRouter(config)# end\nRouter# show running-config interface GigabitEthernet0\u002F1\n```\n\n`running-config` is active memory. `startup-config` is what survives reload.\nDo not save a change just because a command was accepted; validate behavior\nfirst, then use `copy running-config startup-config` if the change is approved.\n\n## Read-Only Collection\n\n```text\nshow version\nshow inventory\nshow processes cpu sorted\nshow memory statistics\nshow logging\nshow running-config | section line vty\nshow running-config | section interface\nshow running-config | section router bgp\nshow ip interface brief\nshow interfaces\nshow interfaces status\nshow vlan brief\nshow mac address-table\nshow spanning-tree\nshow ip route\nshow ip protocols\nshow ip access-lists\nshow route-map\nshow ip prefix-list\n```\n\nCollect the specific section you need instead of dumping full config into a\nticket when the config may contain secrets, customer names, or private topology.\n\n## Wildcard Masks\n\nIOS ACL and many routing statements use wildcard masks, not subnet masks.\n\n```text\nSubnet mask       Wildcard mask\n255.255.255.255   0.0.0.0\n255.255.255.252   0.0.0.3\n255.255.255.0     0.0.0.255\n255.255.0.0       0.0.255.255\n```\n\nReview wildcard masks before deployment. A subnet mask accidentally used as a\nwildcard can match far more traffic than intended.\n\n```text\nip access-list extended WEB-IN\n  10 permit tcp 192.0.2.0 0.0.0.255 any eq 443\n  999 deny ip any any log\n```\n\nEvery ACL has an implicit deny at the end. Add an explicit logged deny when the\noperational goal includes observing misses, and confirm logging volume is safe.\n\n## ACL Placement Review\n\nBefore applying an ACL to an interface, answer these questions:\n\n- Which traffic direction is being filtered, `in` or `out`?\n- Is management traffic sourced from a known jump host or management subnet?\n- Is there an explicit permit for required routing, DNS, NTP, monitoring, or\n  application traffic?\n- Are hit counters available from a safe test source?\n- Is there a rollback command and an active console or out-of-band path?\n\nDo not test reachability by removing firewall or ACL protections. Read counters,\nlogs, and route state first.\n\n## Interface Hygiene\n\n```text\ninterface GigabitEthernet0\u002F1\n description UPLINK-TO-CORE\n switchport mode trunk\n switchport trunk allowed vlan 10,20,30\n switchport trunk native vlan 999\n no shutdown\n```\n\nUse clear descriptions, explicit switchport mode, and documented native VLANs.\nOn routed interfaces, confirm the mask, peer addressing, and routing process\nbefore assuming link state means forwarding is correct.\n\n## Change-Window Verification\n\nUse before\u002Fafter checks that match the actual change.\n\n```text\nshow running-config | section interface GigabitEthernet0\u002F1\nshow interfaces GigabitEthernet0\u002F1\nshow logging | include GigabitEthernet0\u002F1|changed state|line protocol\nshow ip route \u003Cprefix>\nshow ip access-lists \u003Cname>\n```\n\nFor routing changes, also capture neighbor state and route tables before and\nafter the change. For ACL changes, compare hit counters from a planned test\nsource rather than relying on a generic ping.\n\n## Anti-Patterns\n\n- Applying a generated config without a device-specific diff.\n- Saving configuration before post-change checks pass.\n- Using a subnet mask where IOS expects a wildcard mask.\n- Applying an ACL to the wrong interface direction.\n- Troubleshooting by disabling ACLs, route policies, or authentication.\n- Pasting full configs into public tools without sanitizing secrets and topology.\n\n## See Also\n\n- Agent: `network-config-reviewer`\n- Agent: `network-troubleshooter`\n- Skill: `network-config-validation`\n- Skill: `network-interface-health`\n",{"name":5,"metadata":24,"description":7},{"origin":25},"community","main","5d0a87185c0e172c3901e2a6e5916b6d544b8b94","skills\u002Fcisco-ios-patterns","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance","https:\u002F\u002Fgithub.com\u002FJunMystery","AI is the typist, I am the architect. Building efficient, secure, and user-centric products through disciplined AI prompt engineering.","2026-11-13 17:41:25",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add JunMystery\u002FAgent-Guidance --skill cisco-ios-patterns",{"tool":39,"command":40},"bunx","bunx skills add JunMystery\u002FAgent-Guidance --skill cisco-ios-patterns",{"tool":42,"command":43},"pnpm","pnpm dlx skills add JunMystery\u002FAgent-Guidance --skill cisco-ios-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fcisco-ios-patterns\u002FSKILL.md",true,[],[48,54,60,66,72,78],{"skillNo":49,"name":50,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M79QR1E309VJ6CTQKB32AWWA","zero-trust-architecture-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-architecture-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M79QQV7GHYR02DYGN41S23WN","xss-filter-evasion-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxss-filter-evasion-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M79QQNSN7YB8XB61FFSCS3WH","xs-leaks-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxs-leaks-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M79QQHZZJKFDY9132G5A65C2","xpath-injection-prevention-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxpath-injection-prevention-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M79QQB9ZSD3DJG8658EHQXR1","xml-security-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxml-security-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M79QQ60WKV7PFMXWT9CW8PM6","xml-external-entity-prevention-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxml-external-entity-prevention-cheat-sheet\u002FSKILL.md",[],[]]